IIS7 setting strategy on Vista

When IIS7 was first used, it was confusing and there were no attribute forms that were originally familiar with. Instead, there were some unfamiliar terms and operation methods. if you do not comment on this change, it is good or bad. Let it run for us first (the old iron machine runs the Chinese version of Vista, so the terms are based on the Chinese version, if you are using a friend of another version, check for ^! ^ ):

First, install IIS7: IIS7 is not installed by default in Vista, so we need to click "enable or disable Windows" in "programs and functions" in "Control Panel ", hook up the corresponding IIS functions in it. The blacksmith tells you that if you want IIS7 to run ASP. NET 1.1 program, you need to select these options for IIS6 compatibility.

The second is configuration. for ASP. for NET2.0, everything should be simpler, because IIS7 supports ASP by default. for the NET2.0 program, you only need to re-create an application pool and select it. net Framework Version 2.0, managed pipeline method: Classic. This should be OK.

For ASP. NET 1.1 is much more complicated, because IIS7 is generally in. NET FrameWork 1.1, so use: % windir % Microsoft. NETFrameworkv1.1.4322aspnet _ regiis-I to register your. NET FrameWork 1.1, but when you view your site, you only need to run ASP. NET page, IIS will be suspended, at this time, old tie through a lot of practices and search can be very responsible to tell you. After the installation, add the corresponding application pool in the pool, and then set the site. Everything is OK.

Next, let's talk about ASP settings. As a classic WEB framework, sometimes we have to put some ASP pages on our own machine. So let's make IIS7 support ASP together: first, check whether ASP support is installed. In "enable or disable Windows", check the corresponding items in the Web Services and application development functions of IIS, at this time, ASP options are available in the site. ASPClassic will be available in the IIS program ing, which should be disabled by default. In this case, edit the running permission and enable it. If you still cannot view it at this time, the permission is still insufficient. You can modify it in the following way: add the Users permission to Temp under C: UsersDefaultAppDataLocal. At this time, it should be OK (because I made this setting a long time ago, so some of them are not clear, but this setting is much easier than ASP. NET 1.1 ).