Glad you found a solution.
Not correct. Collections (the ones with a list of values, such as
httpHandlers, httpModules, even buildProviders) are item lists whose
ordering and effective value depend on where it merges into the entire
web.config hierarchy. In other words, the above definition simply says
do not see it, there are at least two other .config higher in the
hierarchy which provide values for httpHandlers.
So, all you have done is to append a new httpHandler for the
application that your web.config applies to.
If you wanted to make sure that httpHandlers applicable at that scope
contains ONLY your new httpHandler, you'd use:
/>
However, you'd probably find other things that break when you do
this...
In other words, when you are tweaking these values, you need to know
the exact net-effect of what you are doing.
Well, I'm wager that maybe it is because not many people execute
ASP.Net code using another file extension - they'd just use .aspx,
which is pre-configured and working... so, you're probably doing
something that few people do, and those that do, know about
BuildProviders because they are writing custom ones.
When it comes to modifying httpModules and httpHandlers, I would not
assume that the same syntax provides the same behavior from version to
version. For example, it all changes once again in IIS7 for other good
reasons. So, for any given httpHandler/httpModule collection, it could
have different behaviors on ASP.Net 1.0/1.1, ASP.Net 2.0, and IIS7.
//David
http://w3-4u.blogspot.com
//