There's nothing to screw up as far as IIS is concerned.
The only things I can think of are:
1. there is a cache between you and the ISP with the older response (either
it's a caching proxy, or the ISP somehow still had an older, cached copy of
your DLL which had this problem)
2. you're not uploading the changed DLL to them
3. the older DLL was in-memory, so you cannot overwrite it with your new DLL
until it is unloaded. Once ASP.Net loads a DLL to service a request, it
will never unload that DLL (i.e. you can't change the DLL on disk) until
that process recycles and no other requests cause the DLL to load again.
--
//David
IIS
This posting is provided "AS IS" with no warranties, and confers no rights.
//
"Bruce W..1" <bruce.TakeThisOut@noDirectEmail.com> wrote in message
news:3FCD50ED.79A9C9CE@noDirectEmail.com...
Kristofer Gafvert wrote:
>
> Hello,
>
> Please see this webpage for how to change this:
>
<font color=purple> > <a style='text-decoration: underline;' href="http://builder.com.com/5100-6373-1046325.html</font" target="_blank">http://builder.com.com/5100-6373-1046325.html</font</a>>
>
> --
> Regards,
> Kristofer Gafvert
> Reply to newsgroup only. Remove NEWS if you must reply by email, but
please
> do not.
> <a style='text-decoration: underline;' href="http://www.ilopia.com" target="_blank">www.ilopia.com</a> - FAQ and Tutorials for Windows Server 2003
>
===========================================================
Yes I know all about that. And like I said, it doesn't work right.<!-- ~MESSAGE_AFTER~ -->
>> Stay informed about: Can a webservice namespace be changed in IIS? 
FAQ
Profile
Private Messages
Log in
