Configure pseudo-static IIS 7.5

1) First, create an application pool with any name, for example, nettest. The managed pipeline mode is set to the integration mode temporarily, and then set it to the classic mode after the following series of settings are complete;
2) Deploy the site and set the application pool of the site to nettest;
3) Select the site, switch to the function, find "server components"-> "handler ing", double-click it, and set it in the Action column on the right of the window:
4) "add script ing": Request Path. html: select C: \ Windows \ Microsoft as the executable file. NET \ Framework \ v2.0.50727 \ aspnet_isapi.dll. If it is 4.0, It is C: \ Windows \ Microsoft. NET \ Framework \ v4.0.30319 \ aspnet_isapi.dll. The name is random;
5) "add wildcard script ing": Request Path *. The executable file is C: \ Windows \ Microsoft. NET \ Framework \ v2.0.50727 \ aspnet_isapi.dll. The name is random;
6) "add managed handler": Request Path *. Executable File: System. Web. UI. PageHandlerFactory. The name is random;
7) Open the website switch function, find "server components"-> "module", double-click it, and click "add managed module", Type
URLRewriter. ModuleRewriter, and selects "Send request calls only to asp.net applications or managed handlers;
8) Finally, find the application pool nettest created in step 1 and set the managed pipeline mode to the classic mode.
After completing the preceding steps, you can perform pseudo-static operations under IIS 7.5.

IIS7.5 pseudo-static web. config configuration error

Test A website written in pseudo-static mode locally. the pseudo-static configuration is IIS7 pseudo-static web. config configured in this way. However, a configuration error is prompted during Website access. After deleting the web. config rewrite node of the website, the website can be accessed, but it does not support pseudo-static. This method is intended for the IIS7 version? In addition, it is okay to upload this website to my IIS7 server, so I was wondering if some IIS7.5 plug-ins were not followed. The reason is found through the method because I have not installed URL Rewrite in IIS7.5. First, you can turn off IIS after local installation, and then re-open it. Then the code website that adds the website to the rewrite node is also normal.
: Http://www.iis.net/download/URLRewrite

Windows 7 IIS7.5 local test pseudo-static (Rewrite)

After changing the space, I learned a lot about new things. The VM of Fengyun Internet supports some components not supported by other spaces. In the past, the space did not support ASPJPEG, pseudo-static (Rewrite) is not supported. Currently, all new spaces are supported.

Pseudo-static is a good thing, and it is very useful. I don't need to talk about it much. There are many discussions on pseudo-static on the Forum. In fact, pseudo-static is not a mysterious thing, it is easy to use some rules. There are many rules written on the Internet, so you can study them.

In the past, due to the impact of the test environment, it was generally not tested locally, but all of them were put for debugging in real website space, which also brought a little trouble to debugging, upload and download, this is a waste of time, so I want to study pseudo-static data locally.

There seems to be very little introduction to the pseudo-static IIS7.5 in Windows 7, generally IIS7.0 in Vista, but the difference between IIS7.0 and IIS7.5 is not great, however, it is a little troublesome for me to directly jump from IIS5.1 to IIS7.5, and the change from 5.1 to 7.5 is quite big.

The following describes the installation of pseudo-static (Rewrite) in IIS7.5. The installation is silly. Download this component and install it directly. I downloaded on the IIS official website, I under the 1.1 version now 2.0RC version has come out, but for the sake of stability, I still use 1.1,: http://www.iis.net/expand/URLRewrite

After the installation is complete, open IIS and you will see the URL rewrite option in the IIS configuration of the website.

Double-click the URL rewrite icon (the premise is to select the local test website directory under the "website" directory on the left to use the pseudo-static directory), and then go to the rewrite Management page;

Then we enter the rewrite rule management page;

Click Add Rules to go to The Add Rule Page. Of course, the simplest method is to write a *. htaccess rule file locally, and click Import Rules to Import it.

However, the rewrite rules tested locally are different from those uploaded to the space. For example, my local regulation isRewriteRule coolsite.html LoadMod.asp?plugins=CoolSiteIn real spaceRewriteRule coolsite.html LoadMod\.asp\?plugins=CoolSiteSome rules that I use to write regular expression matching are also different from those that are uploaded locally to the space. The problem of absolute paths relative to paths also makes me explore for a while, I don't know whether the rules I wrote have limitations or are originally like this. I hope some experts can give me some answers.

I did not test it in the main blog. I used my test blog for debugging.