Issue 1: Unrecognized attribute "TargetFramework". Note that property names are case-sensitive.
Symptom: Unrecognized property "TargetFramework". Note that property names are case-sensitive.
Cause: The Web deployed in the site uses the. NET Framework2.0 application Pool, and the virtual directory is based on the. NET Framework4.0
Workaround:
(1) Select the "Application Pool" different from the site , 1;
(2) The version of the ASP is transferred to "4.0.30128", 2;
Figure 1
Issue 2: handler "extensionlessurlhandler-integrated-4.0" has an error module "Managedpipelinehandler" in its module list Deploy the MVC Web site on IIS, open the post-extensionlessurlhandler-integrated-4.0 solution
Deploy the MVC Web site on IIS, open the post-extensionlessurlhandler-integrated-4.0 workaround
An MVC Web site is deployed on IIS, open after 500 error: Handler "extensionlessurlhandler-integrated-4.0" has an error module "Managedpipelinehandler" in its module list
Here's how to fix it:
Register with the administrator to run the following command:
32-bit machine:
C:\Windows\Microsoft.NET\Framework\v4.0.30319\aspnet_regiis.exe-i
64-bit machine:
C:\Windows\Microsoft.NET\Framework64\v4.0.30319\aspnet_regiis.exe-i
An error occurred on MVC Publishing to a virtual host