Workaround for ASP. NET deployment to IIS FAQ _ Practical Tips

This article is mainly for the people to introduce in detail ASPThe workaround for deploying to IIS common problems has some reference value for ASPInterested in the small partners can refer to

Today, Umbraco, in the Local has been done, the results put into the server but there is an exception. Web site to find a lot of information, and ultimately to solve the problem.

Under the solution, the specific problems are not listed;

1. The corresponding. NET Framework framework is not installed

Solution: frameworks below. NET 3.5 are installed by using the "turn Windows features on or off" area.

More than 4.0 of the framework to be downloaded through the official Microsoft website later installed.

2. IIS is not registered successfully

Solution:

In the cmd form, run the following command:

. NET 2.0 Framework Registration:

C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\aspnet_regiis.exe-i

. NET 4.0 Registration (4.5 Framework registration is also the following command, the 4.0 and 4.5 frameworks are displayed in IIS for 4.0):

C:\WINDOWS\Microsoft.NET\Framework\v4.0.30319\aspnet_regiis.exe-i

3, the Site Directory permissions issues

Solution:

Right-click the Web site folder, select Security, and then tap Edit – Add – Advanced – Find now to locate Network service and then "OK", and then give the "Network SERVICE" permission to read, write, modify, etc., if the site still cannot be displayed, then " The NETWORK SERVICE gives you the highest permissions. If complete or not, add "Everyone" and give the highest privileges.

If the above operation is still 404 or the site does not display anything, you can modify the IIS "ISAPI and CGI display" settings, change the restrictions inside to allow it. Such as

The deployment of an ASP. NET site, first make sure that IIS is installed correctly, and then make sure that the site's selected application pool and the Web site have the same version number. If the error is usually checked in the order above, the problem is solved. When you're done with each step, remember to restart IIS and sometimes solve the problem.