Talking about the installation process of IIS7 under Win Vista

On the installation process of IIS7 under Win Vista

On the installation process of IIS7 under Win Vista, the initial use of IIS7 makes people confused, no longer The original familiar property form, instead of some strange nouns and operations. Now do not comment on whether this change is good or bad, let it run for us first:

IIS 7.0 ten Big improvements:

1. Easier command line configuration features

2. Stronger compatibility

3. Discard MetaBase

4. Concentrate Management

5. Appointment Configuration

6. AppCmd ​​and Other New Management Means

7. Failed Request Tracking

8. Request Filtering

9. UNC Content Support

10. Dynamic Content Output Cache

So, which versions of Windows Vista support IIS7? Let's take a look at the following picture:

The initial use of IIS7 makes people confused, and there is no familiar property form, instead of some strange nouns and operation methods. Now don't comment on whether this change is good or bad. Let it run for us first:

First install IIS7: Vista defaults to IIS7, so we have to "Control Panel" Inside the "Programs and Features" click "Open or Close Windows Features", inside the corresponding IIS function hook, friendship prompts, if you want IIS7 to run Asp.Net 1.1 programs, you need to make IIS6 compatible These options are selected together. After clicking "OK", Vista will start the installer and restart the computer after completion.

Secondly, configuration, for ASP.NET2.0, everything should be simpler, because IIS7 supports ASP.NET2.0 programs by default, but you need to rebuild an application pool yourself. Good. Net Framework version 2.0, the way to manage the pipeline is selected: classic. This should be OK.

For ASP.NET 1.1, it is much more complicated, because IIS7 is usually installed after .NET FrameWork 1.1, so use: %windir%Microsoft.NETFrameworkv1.1.4322 Aspnet_regiis -i to register your .NET FrameWork 1.1, but when you view your site, as soon as you run the ASP.NET page, IIS hangs. At this time, the author can go through a lot of practice and search. Tell you responsibly. After loading these, add the corresponding application pool in the pool, then set up the site, everything is OK.

Next, talk about the ASP settings, as a classic WEB framework, sometimes you have to put some ASP pages on your own machine, so let us let IIS7 support ASP: first See if you have installed ASP support, or in the "open or close Windows function", the World Wide Web service under IIS, the application development function inside the corresponding item check, this time there is ASP option in the site In the IIS program map there will be ASPClassic, the default case should be disabled, this time to edit the run permissions, enable it. If you can't view it at this time, it should be the permission is not enough, you can modify it in the following way: Temp in C:UsersDefaultAppDataLocal plus User permissions. This should be OK (because I set this up a long time ago, so some of the notes are not clear, but relatively speaking, this setting is much easier than ASP.NET 1.1).