This section highlights some of the important things to
consider when we are deploying the application.
Make sure the Web.Config setting is perfect, such as connection strings,
App setting values, check <compilation debug="false"/> because
setting it to true causes the application to be processed slow, memory
consumption is more, scripts and images downloaded from the WebResources.axd
handler are not cached.
To trouble shoot the error if it occurred use <CustomErrors>
section in Web.Config and make sure you are reverting back to the original
If we are running multiple versions of ASP.net on the same webserver do
not use aspnet_regiis utility with –i switch to register the ASP.net with the
IIS, instead use –s switch and register it for the particular site because using
–i switch is going to update the entire IIS with the current version of ASP.net
you are registering leaving the existing application configuration affected. For
example, Aspnet_regiis –s W3SVC/1/ROOT/Test.
By default, IIS does not allow dynamic contents like ASP\ASP.NET to be
processed by IIS. So to allow this, Open IIS manager, click Web Service
Extensions and Allow the Web Service Extensions if it is disabled as shown in Figure
14. If there is no extensions for processing ASP.net 2.0 application, we can
add a new web service extension by clicking "Add a new Web service
extension" link. Read more on MSDN on how to add web service extensions in
Figure 14 - Web service Extensions