IIS pseudo-static, support for. NET MVC

This week two encounters with IIS deployed. NET MVC, does not support pseudo-static, reported 404 errors.

Note that the memo, because sometimes anxious to find a content, it is difficult to find.

1, my colleague's computer encountered, originally our development machine, installed after the VS or add to install MVC, will not appear this problem.

My colleague was due to IIS unloading the reload after a problem.

2, my friend company's small website, uses the XX cloud server (I did not advertise), this does not support very normal.

The following solution is also reference to other great God's articles, not original, purely their own memo.

1. Select the site, switch to function, find "IIS (server Components)", "Handler mappings", and then double-click.

Right "Add script map": Request path *, executable file Select C:\Windows\Microsoft.NET\Framework64\v4.0.30319\aspnet_isapi.dll, name is arbitrary.

32-bit, should be C:\Windows\Microsoft.NET\Framework\v4.0.30319\aspnet_isapi.dll. Same below

2, "Add Wildcard script Mapping": Request path *, executable file: C:\Windows\Microsoft.NET\Framework64\v4.0.30319\aspnet_isapi.dll, the name is arbitrary.

3, "Add managed Handler": Request path *, executable file: System.Web.UI.PageHandlerFactory, the name is arbitrary.

4. Select the site, switch to the feature, try to find the "IIS (server Components)", "module", and then double-click.

On the right "add managed module", the name is arbitrary, the type Urlrewriter.modulerewriter, and the "make a request call to an ASP. NET application or managed handler" is selected.

Having done this, my colleague's IIS has access to the MVC page.

But today friend's server, also reported in its module list has an error module "Managedpipelinehandler"

1. Start and all programs, accessories, command prompt, right-click, run as Administrator, execute

2. CD C:\Windows\Microsoft.NET\Framework64\v4.0.30319

3, Aspnet_regiis.exe-i

Get

IIS pseudo-static, support for. NET MVC