You will just have to run either HANDLES.EXE (from
www.sysinternals.com) or
TLIST.EXE (from MS Debugging Tools at
http://www.microsoft.com/ddk/debugging ) to determine which process has a
handle open to your DLL, then stop those processes. Once you stop the
processes that have an open handle to your file, you can replace it.
Unregistration of a DLL is usually not at all related to whether a handle is
open to it or not, so I'm not surprised that it doesn't seem to do what you
are imagining.
At any time, you can first MOVE the old file to a new location/name, then
copy over your new file. Any new users will use the new file, and when the
old users finish up, you can delete it later-on. i.e. to replace a file,
you don't need to do it right then and there.
--
//David
IIS
This posting is provided "AS IS" with no warranties, and confers no rights.
//
"CF CAG" <ronaldo.johnson.RemoveThis@conagrafoods.com> wrote in message
news:013a01c37d40$8049b940$a401280a@phx.gbl...
Hello :
I am running into similar problem posted earlier by Roger
on 09/17/2003. I am unregistering my dlls but still does
not release them. Usually I unregister them and restart
IIS, and that is enough to replace my dlls. I ran IISreset
to do the server retart and still I get the "sharing
violation" error... I actually have to restart the
computer in order for the release to take effect. I am not
able to see which dlls the server is locking wiht the
utility listdlls.exe, for some reason it says I do not
have enoght permission to run this application
(listdlls.exe).
If anyone has any idea of what may be the source of my
problem, I will appreciate it, thanks in advance
ronaldo
>> Stay informed about: IISreset 
FAQ
Profile
Private Messages
Log in
