Wiley 978-0-470-09782-3 Arkusz Danych

Part I: Introduction andDeploymentChapter 1: Background on IIS and New Features in IIS 7.0Chapter 2: IIS 7.0 ArchitectureChapter 3: Planning Your Depl

Figure 1-1Within the IIS 7.0 pipeline, each process is handled by an individual component. These components canbe specifically loaded for those sites

Figure 1-2ConfigurabilityAnother and more visible change is the integration of IIS configuration into the same process used forconfiguring ASP.NET app

Using applicationHost.configThe applicationHost.config file, new in IIS 7.0, stores IIS configurations for both the web server andthe process model. G

There are two great benefits to this new configuration style in IIS 7.0. The first is that by not using theregistry for configuration, deploying a sit

<section name=”MyNewModule” />...</configSections>With these simple changes to the configuration files, you’ve added the custom module My

Minimal InstallationIIS 7.0 continues the tradition of its predecessor with minimal installation the default. IIS is not installedwith the default ope

Management DelegationManagement of IIS in previous versions meant either granting local administrator privileges to the useror working through WMI and

</security></system.webServer></location>To allow the same developer on the same site to enable or disable Windows authentication bu

control, which was prohibitive in an Internet environment. It also allows, with the extensibility of thepipeline components, developers to create thei

<requestFiltering><hiddenNamespaces><add hiddenDirectory=”BIN” /></hiddenNamespaces></requestFiltering></security>

97823c01.qxd:WroxPro 2/4/08 6:47 PM Page 2

IIS ManagerThe new IIS Manager for IIS 7.0, shown in Figure 1-4, combines all management functions for both IISand ASP.NET in one location. Administra

Figure 1-5AppCmd.exe Command-Line UtilityIIS 7.0 introduces a new command-line utility, AppCmd.exe, which replaces the functionality providedby the va

ASP.NET Management NamespaceIIS 7.0 may be configured through the new ASP.NET namespace, Microsoft.Web.Administration,which is used for administration

Set oBinding = oService.Get(“BindingElement”).SpawnInstance_oBinding.BindingInformation = “*:80:”oBinding.Protocol = “http”oService.Get(“Site”).Create

IIS 6.0, in case your application is not able to run in the new IIS 7.0 integrated pipeline mode. Secondly,an optional IIS 6.0 Metabase Compatibility

tion are on a server that was upgraded to Longhorn or have been migrated to a new installation ofLonghorn, you may need to create new accounts and ass

SummaryIIS 7.0 is an evolution of previous IIS versions, building on their strengths while overcoming their weak-nesses. Microsoft has listened to use

Background on IIS and NewFeatures in IIS 7.0Microsoft’s Internet Information Services (IIS) has been around for more than a decade, from itsfirst inca

IIS Versions 1.0 to 4.0IIS was released with Service Pack 3 for Windows NT 3.51, as a set of services providing HTTP, Gopher,and WAIS functionality. A

IIS 6.0IIS 6.0 shipped with Windows Server 2003 editions and Windows XP Professional 64bit edition, whichwas built on the Windows Server 2003 Service

application pool, providing stability across the server’s sites. In addition, worker processes could beassigned a processor affinity, allowing multipr

The FTP service that ships with Windows Server 2008 is exactly the same as shipped in Server 2003.However, the Microsoft IIS development team is also

1 The N editions of Windows Vista are for release in the European Union and do not include an embedded Windows Media Player.IIS 7.0 FeaturesIIS 7.0 is

ment, third-party sources, or even Microsoft. Since these modules and additional programs can beplugged into IIS at any time, without changing core op