Last post Feb 09, 2010 12:19 PM by BBuzzi
Feb 09, 2010 06:46 AM|BBuzzi|LINK
I have an application which uses third party components. These components uses an HttpModule to handle errors on callback. I have my own HttpModule to log errors.
Since they both get exceptions, I thought that by registering my HttpModule first in web.config it would work, but it doesn't.
Here's my web.config:
<add name="ScriptModule" preCondition="managedHandler" type="System.Web.Handlers.ScriptModule, System.Web.Extensions, Version=220.127.116.11, Culture=neutral, PublicKeyToken=31BF3856AD364E35"/>
<add type="WebComercial.App_Codes.ErrorHttpModule,WebComercial" name="ErrorHttpModule"/>
<add type="DevExpress.Web.ASPxClasses.ASPxHttpHandlerModule, DevExpress.Web.v9.2, Version=18.104.22.168, Culture=neutral, PublicKeyToken=b88d1754d700e49a" name="ASPxHttpHandlerModule"/>
Could somebody tell me how can I get this to work?!
Thanks a lot!!!
Feb 09, 2010 10:20 AM|Matt-dot-net|LINK
I don't think you can make this work. I think only one module can handle the application error event. I think there is a limitation of the framework itself but it might also be because of Server.ClearError()
Feb 09, 2010 12:19 PM|BBuzzi|LINK
I've got the source code from the third party HttpModule.
It doesnt handle the application error event, I'll override it so it'll let my module work togheter.
Thanks for the reply.