Some issues that occur with ASP. NET configuration on IIS

1. You may encounter a mistake without. The requested content appears to be a script. As a result, the static file handler will not be able to handle the---probably because the application pool selection is wrong. As the second picture solves, you can

The solution is shown in the following two diagrams.

I have encountered the above problems and can also encounter the "IIS apppool\asp.net v4.0 Login Failed" error (I use: NET Framework 4.0, so this error is reported). My solution is to select in the application pool in IIS Manager

The---> Advanced options for ASP. NET V4.0 are found---set built-in accounts-----> for LocalSystem. Shown below,,

At the same time, the permissions of the folder under the path of the Web site are also set to the highest permissions----Full Control-Set steps--Folder---Properties---security--edit---add--enter Everyone in the input object name--click Check Name--OK

Z

So boring...

There is also a problem with IIS.

1, because the first installed. When IIS is installed after netframework, 4.0 of related handlers are not registered to the IIS Server Software.
Workaround: Find cmd in the Start menu, cd\ command to the physical path of aspnet_regiis.exe, enter Aspnet_regiis-i manual registration to resolve

Aspnet_regiis.exe physical path in: (with 32-bit system and 64-bit system points)
C:\Windows\Microsoft.NET\Framework\v4.0.30319\aspnet_regiis.exe

Some issues that occur with ASP. NET configuration on IIS