Chapter 5. Extending the Integrated Configuration System and Imperative Management API

The previous chapters provided in-depth coverage of the following four important components of the IIS7 and ASP.NET integrated infrastructure:

  • IIS7 and ASP.NET integrated configuration system

  • IIS7 and ASP.NET integrated graphical management system (IIS7 Manager)

  • IIS7 and ASP.NET integrated imperative management system

  • IIS7 and ASP.NET integrated request processing pipeline

As discussed, the modular architecture of the IIS7 and ASP.NET integrated request processing pipeline allows you to plug your own custom feature modules into the integrated pipeline to add support for new custom processing capabilities. Adding a new custom feature module also requires you to:

  • Extend the IIS7 and ASP.NET integrated configuration system to add support for a new configuration section to allow the clients of your custom feature module to configure the module from configuration files

  • Extend the IIS7 and ASP.NET integrated graphical management system (IIS7 Manager) to add support for new graphical components to allow the clients of your custom feature module to configure the module from the IIS7 Manager

  • Extend the IIS7 and ASP.NET integrated imperative management system to add support for new managed classes that allow the clients of your custom feature module to configure the module from their C# or Visual Basic code in a strongly-typed fashion.

Therefore, extending the IIS7 and ASP.NET integrated infrastructure requires ...

Get Professional IIS 7 and ASP.NET Integrated Programming now with O’Reilly online learning.

O’Reilly members experience live online training, plus books, videos, and digital content from 200+ publishers.