Deploying Web Applications
In the previous three chapters you learned to develop Web applications and Web services with ASP.NET. For all these application types, different deployment options exist. You can copy the Web pages, publish the Website, or create an installation program. This chapter covers the advantages and disadvantages of the different options, and how to accomplish these tasks.
In this chapter, you learn about:
- Internet Information Services
- IIS configuration
- Copy Websites
- Precompiling Websites
- Windows Installer
Internet Information Services
Internet Information Services (IIS) needn't be installed for developing Web applications with Visual Studio 2005 because Studio 2005 has its own Web server: the Visual Web Developer Web Server. This is a simple Web server that runs only on the local machine. On the production system, IIS is needed to run the Web application.
Now look at how IIS and ASP.NET fit together. Figure 21-1 shows Windows XP's process model. IIS is running in the inetinfo.exe process. This process has an ISAPI extension for ASP.NET that uses configured file extensions to pass requests from the client to the ASP.NET process aspnet_wp.exe. By default, IIS's processes run with System account privileges, while the ASP.NET runtime runs with the nonprivileged user aspnet.
An ISAPI extension is a DLL that is running in the process of the Web server.