Today I am looking into setting up IIS 7 on a new Windows 2008 server and getting it to serve an ASP.NET 2.0 built Web Site. I am used to doing this using IIS 6 on Windows 2003, but it looks like things have changed quite a bit with IIS 7.
In my case the IIS 7 setup on Windows 2008 has to happen on a remote server so before I start configuring things I am testing setting up IIS 7 on my development machine which is running Windows 7. I am hoping this will give me a good basis even though the version of Windows is different.
I found a good article on TechNet that gives an overview of both installation methods. This article can be found at:
These are the steps I just went through when setting up IIS 7 on my Windows 7 machine:
1) I click ‘Start’, then ‘Control Panel’, and then browse to ‘All Control Panel Items’. (** Did I mention how irritating I find the new Windows ‘Feature’ of limiting what one sees under the traditional ‘Control Panel’ so that one has to default to ‘All Control Panel Items’ now instead).
2) Then click ‘Programs and Features’, and in the pop-up window click on the option ‘Turn Windows Features On or Off’.
3) In the new pop-up window expand the node ‘Internet Information Services’, then the node called ‘World Wide Web Services’, and then all of the sub-nodes. There will be a number of options, the core of which that need to be checked are:
- Application Development Features\ASP.NET
- Application Development Features\.NET Extensibility
- Application Development Features\ISAPI – I turned on both ISAPI Extensions and ISAPI Filters
- Security\Request Filtering
4) In addition, I selected the following options which I thought would be important:
- Common HTTP Features\Default Document
- Common HTTP Features\HTTP Errors
- Common HTTP Features\Static Content
- Health and Diagnostics\HTTP Logging
- Health and Diagnostics\Request Monitor
- Performance Features\Dynamic Content Compression
- Performance Features\Static Content Compression
5) Once the options are selected click ‘OK’, and follow the installation instructions to complete the setup.
6) Once this is complete one should be able to browse to localhost and insert & run a test .aspx file
This should complete the base installation of ASP.NET for the server.
The next step is to set up a properly configured Web site, which may be a bit of a challenge since Microsoft has so completely altered the interface. For example, in IIS 7 Microsoft has moved the Application Pools section which I am still working on tracking down. Luckily the WebService Extensions section remains intact so I can specify what version of ASP.NET I would like the application pool for my site to run under.