Professional ASP.NET 3.5 AJAX

16.4. Avoiding Common Configuration Problems

Now, that you've ensured that the requisite packages are installed on your production machine, you should guard against some common pitfalls before proceeding directly to application deployment. This is a key part of the predeployment checklist. Many of the problems in deployment turn out to be errors in the configuration files. Much of the behavior of ASP.NET can be adjusted in the machine.config and web.config files. One change to the root machine-level configuration can have a negative impact on all of the applications running on the server. If you change a setting in these files to gather information during development and forget to return it to the default before rolling out to production, you may face performance or security problems.

16.4.1. Disable Debugging

When developing a Web application, you often want to be able to step through code as it is running in order to find problems. When launching a Web application for debugging, Visual Studio will remind you, as shown in Figure 16-2 that Internet Explorer needs to have script debugging enabled. Leaving it enabled may affect your experience with other applications when script errors are encountered, but it won't have any adverse impact on your application itself.

Figure 16-2. Figure 16-2

Visual Studio will even offer to automatically modify the web.config file to enable debugging. ...