When I used the
As a workaround, I added the following line whilst configuring my NSB endpoint:
endpointConfiguration.CustomDiagnosticsWriter(s => Task.CompletedTask);
I have a template application which exhibits this behaviour if it makes fixing this issue any easier, although you can add the following to any class in your App_Start folder:
var endpointConfiguration = new EndpointConfiguration("nsbEndpoint");
endpointConfiguration.SetDiagnosticsPath($@"{AppDomain.CurrentDomain.BaseDirectory}bin\.diagnostics");
endpointConfiguration.UseTransport<SqlServerTransport>().ConnectionString(cnnctnstrng);
endpointConfiguration.UsePersistence<InMemoryPersistence>();
Endpoint.Start(endpointConfiguration).GetAwaiter().GetResult();
Then, try refreshing the page.
NSB, version 7.1.4
Transport: SQL Transport, version 4.1.0 (likely also happens on other transports)
@chipolatas It sounds like what you're experiencing is exactly why we don't use the bin folder by default when we detect you're running an ASP.NET application. We default to the App_Data folder instead.
The reason for this is that ASP.NET monitors the bin folder for changes and recompiles the application when anything changes.
If you don't want to use App_Data, you need to use SetDiagnosticsPath to point to some place other than your bin folder.
@bording ahh I wasn't aware ASP.NET did that... completely my fault! Thanks for the quick reply! :)
Most helpful comment
@chipolatas It sounds like what you're experiencing is exactly why we don't use the
binfolder by default when we detect you're running an ASP.NET application. We default to theApp_Datafolder instead.The reason for this is that ASP.NET monitors the
binfolder for changes and recompiles the application when anything changes.If you don't want to use
App_Data, you need to useSetDiagnosticsPathto point to some place other than yourbinfolder.