I’m having some trouble setting the ExecutionTimeout element in my applications web.config.
My page is making a lengthy webservice call and times out after 110 seconds. (the default I believe). I set the value to 220, and make sure the compilation debug=false.
Does the compilation setting refer to when IIS/ASP.net compiles the ASPX pages when a client requests them, or does it refer to the visual studio compile process there the assemblies are created.
Would using an assembly built using debug in visual studio still allow the above settings to work?
IIS does not compile aspx pages when people request them. If you have a ‘web application project’ in VS, you compile all of your code behinds and other class files before you deploy. If you have a ‘web site project’ in VS, then the web server compiles your app on first request only. After either one of these happen, the application is not compiled again until you make a change.
With that information in mind above, this is when the compilation debug = true | false comes into play. Having debug = true, you get some pretty detailed information back on errors and other events but it can make your app run slower as debug symbols are inserted into the .dll and overall, it is not optimized for performance. By setting debug = false, you don’t get quite the same level of error reporting, but you do get your performance gains back.
If you build in VS, it will build according to the settings in the web.config unless it is an external .dll/class project that you are including. If that is the case, the web.config settings mean nothing to that .dll and will run regardless of what combination of debug = false|true you have on those two projects.