Last post Mar 09, 2010 02:40 PM by NaR883
Jan 02, 2008 02:14 PM|andrew_|LINK
I'm looking for an explanation as to the functional difference between implementing an IHttpHandler (and setting up a file.axd entry in web.config) and using the vs.net ASHX handler template. I've run across a flash component that I'm using for uploading
and it requires a file path in which to POST to. I ran across an issue where my IHttpHandler implementation wasnt functioning properly with it, but the same code in an ASHX template seems to. The developer has suggested that its something to do with the implementation
in each, respectively.
So can anyone outline the differences between the two?
Jan 07, 2008 06:05 AM|Guang-Ming Bian - MSFT|LINK
You should actually be able to use either extension -- both can be mapped to your own custom IHttpHandler.
I would prefer to go with a .ashx extension. One reason for this is that there are no built-in .ashx end-points in ASP.NET -- whereas there are a few .axd ones (for example: the new webresources.axd). So going with a .ashx reduces the chance of a naming
.ashx files also now have intellisense support in VS 2005 -- so that makes building them easier as well.
Guang-Ming Bian - MSFT
Mar 09, 2010 02:40 PM|NaR883|LINK
I'm sorry Guang-Ming, but I don't like plagiarism: