Datasheet
This integrated configuration system provides a lot of benefits to system administrators and developers
alike. For one thing, both IIS and ASP.NET configuration settings are stored in storage media with the
same schema. This is great news for ASP.NET developers because the new integrated schema is an
extension of the ASP.NET configuration schema. Another obvious benefit of the integrated configura-
tion system is that you can use the same set of APIs to programmatically access and set both IIS 7 and
ASP.NET configuration settings.
One of the great new features of the IIS 7 and ASP.NET integrated configuration system is its declarative
extensibility through a new integrated declarative schema extension markup language. Thanks to this
integrated markup language, you can extend this integrated configuration system to add support for
new configuration sections without writing a single line of imperative code such as C# or VB. This is a
departure from the imperative extensibility model of the ASP.NET configuration system, which requires
developers to write a fair amount of imperative code to extend the system.
IIS 7 and ASP.NET Integrated
Administration
Having two separate configuration systems for ASP.NET and IIS in IIS 6.0 also means having two sepa-
rate administration tools, GUIs, and APIs to administer and to manage them. Having a single integrated
configuration system made it possible for the IIS 7 team to introduce brand new administration or man-
agement tools, GUIs, and APIs that make the task of server, site, and application administration a whole
lot easier. This allows you to use the same integrated management tools, GUIs, and APIs to configure
ASP.NET and IIS.
Two very important components of the IIS 7 and ASP.NET integrated administration are the integrated
graphical management system and the integrated imperative management system. This book covers both
of these systems and their extensibility models in detail. You will learn how to extend these two systems
to add graphical and imperative management support for your own custom configuration sections.
Building a Customized Web Server
IIS 7 setup is completely modular, allowing you to custom-build your Web server from a list of more
than 40 available feature modules. This ensures that your Web server contains only the feature modules
you need, thereby decreasing the attack surface and footprint of your server. In this section, I walk you
through the steps that you need to take to build your very own custom Web server on Windows Vista
(including Windows Vista Home Premium, Windows Vista Professional, and Windows Vista Ultimate
editions) and Windows Server 2008 operating systems.
In general, there are five different IIS 7 setup options:
❑ Windows Features dialog (Windows Vista only)
❑ Server Manager tool (Windows Server 2008 only)
❑
pkgmgr.exe command-line tool (both Windows Vista and Windows Server 2008)
11
Chapter 1: IIS 7 and ASP.NET Integrated Architecture
52539c01.qxd:WroxPro 9/17/07 6:51 PM Page 11