I'm sure, like me, you've seen plenty of production web.config files with debug=true set. Most senior ASP.NET developers will recognize that debug should be set to false for the production build. However, this small detail is often over looked. So what does this setting really do and does it have any significant impact on a production site?
When debug is set to true, the following occurs:
Pages are not batch compiled.
Pages do not time out. When a problem occurs, such as a problem with a Web service call, the Web server may start to queue requests and stop responding.
After moving back to Tulsa, OK in late August I began connecting with the local .NET User Group. I was very excited to find a thriving .NET Developer Community lead by David Walker. This year Walker and crew are organizing a two day Technology Festival from October 19th - October 20th. The event has quite an outstanding list of speakers and is FREE!
From what I understand this type of event differs from a Code Camp because it is not purely code focused or even Microsoft focused. I believe the TechFest is meant to discuss real challenges facing IT folks...