IIS7 settings on Windows Vista Raiders

The initial use of IIS7 makes people confused, no longer familiar with the property form, instead of some strange nouns and operation methods. Now do not comment on whether this change is good or bad Let it run for us first (the old iron machine runs the Chinese version of Vista, so the nouns inside are based on the Chinese version. If you use other versions of friends, please look for ^!^):
The first is to install IIS7: Vista default is not installed IIS7, so we have to click "Open or close the Windows
function" in the "Programs and Features" in the "Control Panel", in the corresponding The IIS feature hooks, the blacksmith friendship prompts you, if you want IIS7 to run ASP.Net 1.1 programs, you need to select these options together with IIS6 compatibility.
Second is the configuration, for ASP.NET2.0, everything should be simpler, because IIS7 is ASP.NET2.0 by default, just need to rebuild an application pool, choose .Net The version 2.0 of the Framework, the way to host the pipeline is selected as: 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.4322aspnet_regIIS -i to register your .NET FrameWork 1.1, but this time when you view your site, as soon as you run the ASP.Net page, IIS hangs, and then add the corresponding application pool in the pool, and 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 to see, so let us let IIS7 support ASP: first have to look at Is not installed on the support of ASP, or in the "open or close the Windows
function", the World Wide Web service under IIS, the application development function inside the corresponding item check, this time there is an 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 them are not clear, but relatively speaking, this setting is much easier than ASP.Net 1.1).