Dennis J. Bottjer | MVP ASP.NET

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.
• Additional files are generated in the Temporary ASP.NET Files folder.
• The System.Diagnostics.DebuggableAttribute attribute is added to generated code. This causes the CLR to track extra information about generated code, and it also disables certain optimizations.

Source of Information: http://msdn2.microsoft.com/en-us/library/ms998549.aspx

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 everyday.  For example system integration, security, and architecture.  In large enterprises we often find a mixture of vendor products and the IT staff is tasked with forcing these systems to communicate.  I understand TechFest to be a perfect audience for sharing such experiences.

I am presenting twice at TechFest.  One talk is the "Role of an Architect and the Importance of Design" in the Architecture Track.  My other talk is on Office Business Applications.

Hope to see you at the event.