How to prevent an ASP.NET application restarting when the web.config is modified?

I’m hosting the ASP.NET runtime via the ApplicationHost.CreateApplicationHost method. When I modify the web.config while the application is running, i see lots of first chance ThreadAbortExceptions thrown. This is right before my application comes crashing down. I’m assuming this is because the runtime has detected changes to the configuration and wants to restart.

Logging best practices

I’d like to get stories on how people are handling tracing and logging in real applications. Here are some questions that might help to explain your answer. Frameworks What frameworks do you use? log4net System.Diagnostics.Trace System.Diagnostics.TraceSource Logging application block Other? If you use tracing, do you make use of Trace.Correlation.StartLogicalOperation? Do you write this code … Read more