Comments on Alanta Developer Notes: The mysterious problem with WebResource.axd

Thank you. Your hint (worker process) probably sav...

2010-07-02T18:57:08.849+02:00

Thank you. Your hint (worker process) probably saved me a lot of time.

Thanks for the solution. I was running into some ...

2008-03-24T22:49:00.000+01:00

Thanks for the solution. I was running into some additional problems after your proposed change, but once I resolved all of those it now seems to be working fine.

The point of the note is that you should not overr...

2008-03-21T21:31:00.000+01:00

The point of the note is that you should not override WebResource.axd. ASP.NET needs this URL to map to it's internal handler and it will check your configuration to see if this is the case. If you map webresource.axd to your custom handler instead, ASP.NET will detect this and throw the exception.
By registering your handler after the webresource.axd handler you could get the effect of mapping all urls except webresource.axd to a custom handler.
I hope this helps...

I've inherited some code that has this problem cau...

2008-03-21T19:53:00.000+01:00

I've inherited some code that has this problem caused by the note at the bottom of your blog. Basically the guy wrote a handler that handles every (*) path. The thing is, I'm not quite sure I understand what you are saying the solution is.

He has his handler looking for trace.axd so that it can create the expected handler and use that in that instance, but if I try to do the same thing for WebResource.axd I get the error mentioned above before the code ever even gets to my handler.

Would you mind posting a possible solution for the note at the bottom?