Script not served by static file handler on IIS7.5

前端 未结 23 1467
执念已碎
执念已碎 2020-11-30 21:11

I\'ve just tried to deploy my first web application to IIS on my Windows 7 Home Premium notebook. After creating the application, I had to change to the Classic App Pool, t

相关标签:
23条回答
  • 2020-11-30 21:23

    I had the same issue, I just changed the target framework version on the website to the version it is developed in,Same in IIS. This solved my problem. Hope this helps...

    Thank You

    0 讨论(0)
  • 2020-11-30 21:24

    I had this issue with Windows Server 2012 with ASP .NET 4.5 you can't use aspnet_regiis.exe, and just have to install ASP .NET 4.5 via the Add Roles and Features Wizard:

    enter image description here

    You can find the menu item "Add Roles and Features" in the menu "Manage", in the right corner of Server Manager

    0 讨论(0)
  • 2020-11-30 21:28

    Register asp.net again....will solve the issue.
    enter image description here

    Go to Visual Studio Command Prompt,
    And register asp.net as windows\microsoft.net\Framework[.Net version num]\aspnet_regiis.exe -i

    0 讨论(0)
  • 2020-11-30 21:28

    I stumbled upon this question when I ran into the same issue. The root cause of my issue was an incorrectly-configured app pool. It was set for 2.0 inadvertently, when it needed to be set to 4.0. The answer at the following link helped me uncover this issue: http://forums.iis.net/t/1160143.aspx

    0 讨论(0)
  • 2020-11-30 21:28

    For Windows 10/Framework 4.7, I had to turn on HTTP Activation through the following method:

    1. Control Panel > Programs and Features > Turn Windows Features on or off
    2. Under .NET Framework 4.7 Advanced Services, expand WCF Services, select to check the HTTP Activation and whatever else you need when working with WCF
    3. Click OK and let the install do its thing, then open an administrative command prompt and issue the IISRESET command
    0 讨论(0)
  • 2020-11-30 21:28

    Using IIS manager, I found that .aspx files were mapped (under "Handler Mappings") to ISAPI 2.0 - even though ASP.NET 4.5 had been previously installed. Editing them to point (also) to an executable for ISAPI 4.0 64bit fixed the issue.

    The executable was found in %windir%\Microsoft.NET\Framework64\v4.0.30319\aspnet_isapi.dll

    0 讨论(0)
提交回复
热议问题