Issues caused by installing IIS and the. NET Framework Sequence

Introduction

Recently helped others to do a small web site, in the local deployment test, unexpectedly browsing the aspx suffix of the page, but you can browse the HTML page, this thought of IIS on static pages and dynamic pages of different processing.

HTTP request arrives at server

When the server receives an HTTP request, the IIS needs to decide how to process the request, determine how to process the request based on the suffix name of the file, and after obtaining the suffix name, find an application on the server that can handle the suffix name, if IIS cannot find an application that can handle the file, And this file is not protected by the server side, then IIS will return the file directly to the client. (such as: *.html,*.htm,js,*.jpg,*.png, etc.)

Applications that can handle a variety of suffix names, typically become ISAPI applications (Internet server Applicatin pogram Interface, Internet Servers application programming interfaces). Although it is an application, it is actually an interface that acts as an agent, and its main job is to map the actual handlers of the requested page to the prefix name.

This column more highlights: http://www.bianceng.cnhttp://www.bianceng.cn/Programming/net/

Through the above, and the actual deployment of the problems encountered, can be suspected to be an extender problem, the Extender cannot find the corresponding handler.

Reason

Why does it cause this problem?

Recently reinstalled system, the system installed after the installation of the vs2013 after the installation of IIS caused by the installation of IIS before installation VS, the system will automatically configure IIS, no manual configuration.

Solution

Msdn:http://msdn.microsoft.com/zh-cn/library/k6h9cz8h.aspx

Refer to the MSDN version and re-register. NETFramework.

Open cmd

Find the path to the Framework, my vs default is installed in C disk, the path is: C:\Windows\Microsoft.NET\Framework\v4.0.30319

Enter the CD into the directory, enter the command aspnet_regiis.exe-i

Re-browsing, problem solving.

Summarize

This is in the actual operation of the problem, this problem is not common people can encounter, we are estimated to be the normal sequence of installation, rarely encountered, record, here hope to help meet the same problem with me friend.

Author: wolfy

Source: http://www.cnblogs.com/wolf-sun/