It seems to me that IIS7 doesn't like <soapExtensionTypes>, what is the alternative?

I essentially write errors to ELMAH just like this SO answer suggests , but initially I had an error from IIS suggesting that the setting was not used and then, when I cleared the error (by checking for an outdated configuration check), my hooks, don't seem to be called.

HTTP Error 500.22 - Internal Server Error
An ASP.NET setting has been detected that does not apply in Integrated managed pipeline mode.

Most likely causes:

    * This application defines configuration in the system.web/httpModules section.

I know that some settings, such as system.web / httpModules, need to be transferred to system.webServer, but I cannot figure out what to do with the soapExtensionTypes configuration setting.

<webServices>
  <soapExtensionTypes>
    <add type="ModuleName.SoapExceptionHandler, ModuleName" priority="1" group="0" />
  </soapExtensionTypes>
</webServices>

What do I need to do so that mine SoapExtensioncan load into the pipeline?

Alternatively, I'm just mistaken and it should work, but did I do it?

Update: in my httpModules section I have,

<httpModules>
  <add name="ErrorLog" type="Elmah.ErrorLogModule, Elmah" />
</httpModules>
+3
1

, , ( ).

, , system.web/httpModules web.config.

, web.config( , ..), - .

UPDATE

, Elmah httpModules. :

<webServices>
    <soapExtensionTypes>
        <add type="ModuleName.SoapExceptionHandler, ModuleName" 
             priority="1"
             group="0" />
    </soapExtensionTypes>
    <modules>
        <add name="ErrorLog" type="Elmah.ErrorLogModule, Elmah" />
    </modules>
</webServices>
0

Source: https://habr.com/ru/post/1762473/


All Articles