(go) resolution to detect ASP. NET settings that are not applicable in integrated managed pipeline mode (GO)

We ported the ASP. IIS6 to IIS7, which may be run with the following error:

　　HTTP Error 500.23-internal Server error

　　An ASP. NET setting was detected that is not applicable in integrated managed pipeline mode.

　　Why does the above error occur?

There are two modes of application pool in IIS7, one is "Integrated mode" and one is "Classic mode".

Classic mode is the way we used to be in IIS 6.

If you are using Integrated mode, you will need to change the configuration files for your custom httpmodules and httphandlers to transfer them to <modules> and

　　Two workarounds:

The first method, configure the application pool

Configure the application pool on IIS7 and change the schema of the program pool to "classic", after which everything is fine.

The second method, modify the Web. config configuration file

For example, originally set

<system.web> .......    
When the IIS7 application pool is "Integrated mode", change to
<system.web>    ...........</system.web><system.webserver>    <modules>      <add Name= "MyModule" type= "Myapp.mymodule"/>          </modules>    
If you want to keep the original settings, you can set the Disable Authentication integration mode (validateintegratemodeconfiguration= "false"), which will not cause an error.
(go) resolution to detect ASP. NET settings that are not applicable in integrated managed pipeline mode (GO)