Reading about the IIS 7.0 configuration system might bring fears and worries to you on how to manage both configuration systems and what to count on. In this context there is no magical solution that you can follow when it comes to managing both configuration systems. At the same time, having flexibility and richness with both configuration systems should be a source of power for you as a developer, giving you more control in configuring both the IIS 7.0 and ASP.NET specific features.
For instance, IIS 7.0 contains the CustomErrorModule, a native module running in the IIS 7.0 Web server core engine that maps to the <httpErrors /> configuration section that allows you to define custom HTML/ASPX pages to handle specific errors that might occur during the processing of HTTP requests inside IIS 7.0. The <httpErrors /> configuration section, for example, looks something similar to the following:
<httpErrors> <error statusCode="401" prefixLanguageFilePath="%SystemDrive%\inetpub\custerr" path="401.htm" /> <error statusCode="403" prefixLanguageFilePath="%SystemDrive%\inetpub\custerr" path="403.htm" /> </httpErrors>
The preceding configuration section configures a possible error through its statusCode attribute and maps its handler to an .htm static page. In your application, you can map to a custom .aspx page that is part of the theme and layout of the application you are developing.
Another flexibility is given to you through ...