Does the same work on a non-WebSharper ASP.NET site? In other words, do you believe WebSharper modules are to blame for somehow interfering with ASP.NET pipeline, or is it more of an ASP.NET question?

By on 5/6/2013 6:17 AM ()

No this is definitely not a WebSharper bug, rather the usage I make doesn't give me access to the ApplicationStart of the Global.asax (which is what I want). I would simply have no other way to register a global error handler.

More of an ASP.NET question really, yet abstracting the whole thing away in favor of WebSharper would be a plus as far as I'm concerned :)

By on 5/25/2013 9:20 AM ()

Hi,

With ASP.NET, I would check that:

1. Your code that handles UnhandledException is actually executing.
2. Your application uses only one AppDomain, or your handler registers on every AppDomain.
3. Maybe there is a way to modify Global.asax after all? From this [link:www.asp.net] it seems to be the easiest way to go.
4. You could probably do something like this with an IIS module, but it is a bit more work.

We'll try to give this a better story in WebSharper context.

Thanks,

Anton

By on 5/27/2013 7:03 AM ()
IntelliFactory Offices Copyright (c) 2011-2012 IntelliFactory. All rights reserved.
Home | Products | Consulting | Trainings | Blogs | Jobs | Contact Us | Terms of Use | Privacy Policy | Cookie Policy
Built with WebSharper