Iis7 ASP. NET mvc3.0 deployment problems

1. The application pool adopts the Classic mode, framework4.0. There may be permission issues. Solution: Set the identifier of the advanced settings to LocalSystem.

Generally, MVC adopts the integration mode. Why should I select the Classic mode? Because you need to identify the httpmodules configuration.

2. Open the handler ing settings of IIS, and "add wildcard script ing"

Request Path :*

Executable File: C: \ WINDOWS \ Microsoft. NET \ framework \ v4.0.30319 \ aspnet_isapi.dll

Name: MVC

3. You may also encounter a situation where other pages or JS cannot be accessed in addition to handling routing access. The solution on the internet is as follows:

Set in Web. config

<System. Web>
<Buildproviders>
<Add extension = "*" type = "system. Web. Compilation. pagebuildprovider"/>
</Buildproviders>
<Httphandlers>
<Add verb = "*" Path = "*" type = "system. Web. staticfilehandler"/>
</Httphandlers>
</System. Web>

1. The application pool adopts the Classic mode, framework4.0. There may be permission issues. Solution: Set the identifier of the advanced settings to LocalSystem.

Generally, MVC adopts the integration mode. Why should I select the Classic mode? Because you need to identify the httpmodules configuration.

2. Open the handler ing settings of IIS, and "add wildcard script ing"

Request Path :*

Executable File: C: \ WINDOWS \ Microsoft. NET \ framework \ v4.0.30319 \ aspnet_isapi.dll

Name: MVC

3. You may also encounter a situation where other pages or JS cannot be accessed in addition to handling routing access. The solution on the internet is as follows:

Set in Web. config

<System. Web>
<Buildproviders>
<Add extension = "*" type = "system. Web. Compilation. pagebuildprovider"/>
</Buildproviders>
<Httphandlers>
<Add verb = "*" Path = "*" type = "system. Web. staticfilehandler"/>
</Httphandlers>
</System. Web>