First install vs Reload IIS IIS Publishing Service is unable to browse, prompts for MIME registration _iis

When loading vs reload IIS, discovering that the handler mappings are not registered to IIS can not be browsed with IIS Publishing Service in the following way, prompting for MIME registration

Problem Description:

Error summary
HTTP Error 404.3-not Found
The page you requested is not available due to extended configuration issues. If the page is a script, add the handler. If you should download the file, add a MIME map.
The most probable cause:
The handler mapping may be missing. By default, the static file handler processes all content.
The feature you want to use may not be installed.
The appropriate MIME mappings are not enabled for a Web site or application. (Warning: Do not give the. svc that the user should not download.) ASPX pages or. config files to create MIME mappings. )
If ASP.net is not installed.
What I'm having today is asp.net. Not registered in IIS.

Solutions
Locate the VS2010 command prompt tool, the VS 2008 Command prompt tool, or the VS2005 command prompt tool. Then run as Administrator and enter commands
Aspnet_regiis-i

If you finish, there are also the following errors the error occurred asp.net published to IIS: Handler "pagehandlerfactory-integrated" has an error module "Managedpipelinehandler" in its module list

When you develop a Web project, you need to install IIS, and when you publish the ASP.net Web site on Windows7, where IIS is installed, the Web program is mapped to local IIS, but the following error prompts "handler" pagehandlerfactory-integrated There is an error module "Managedpipelinehandler" in its module list

The Web Project development tool and the system that I am publishing

① Development tools: VS2010, Database: SQL Server

② Operating System: Windows7

③iis:iis 7.5

I. Details of the above error map:

Two. The above error analysis:

VS2010 defaults to the. NET 4.0 framework, the 4.0 framework is separate CLR, and. NET 2.0, if you want to run the. NET 4.0 Framework Web site, you need to register the. NET 4.0 framework with aspnet_regiis, and then use. Net 4.0 Framework's class pool, you can run the. NET 4.0 Framework Web project.

The cause of the above error is most likely due to the installation first. NETFramework v4.0 is caused by installing IIS 7.5.

Three. How to register 4.0 frames with aspnet_regiis.

The method is as follows:

① found the. NET 4.0 framework under the ASPNET_REGIIS directory, in the C-packing directory search aspnet_regiis, find 4.0 frame aspnet_regiis directory location, I directory for "C:\Windows\ microsoft.net\framework\v4.0.30319 ".

② runs the DOS command line as an administrator,

Execute "start → all programs → attachments → command Prompt" (right click to select ' Run as Administrator (A) '), pop-up "Administrator: Command Prompt" window

③ executes the command "CD C:\Windows\Microsoft.NET\Framework\v4.0.30319" and Goes to the "C:\Windows\Microsoft.NET\Framework\v4.0.30319" directory, as shown in

Then execute the command "aspnet_regiis.exe-i", register "aspnet_regiis", wait a moment, aspnet_regiis successfully registered as shown

When you see the interface in the diagram, you can run it in IIS. net4.0 deployed sites.