>Hi,
>
>We are developing a web site hosted in a shared environment by Interland and using some Visual Basic dlls. Whenever we need to make change, we have to do following put our updated new dll into live web site (I have no problem generating the dll)
>in Vadmin,
>(1)unregister the old dll,
>(2)stop the server,
>(3)WAIT 24 HOURS OR EVEN LONGER so that
>(4)we can upload and register the updated dll and then restart the server.
>
>This sounds rediculus. We have to WAIT otherwise simple not able to overwrite the old dll.
>
>I guess we just don't know how to do it correctly. please help...
>
>~Sheldon

You could try hosting the DLL in an MTS package (NT4) or COM+ application (W2K) so that you only need to shutdown the package/application in order to be able to change components. Of course this adds another layer of instantiation, and these additional programs installed and/or configured.

Now, if you are doing these changes remotely that could add some other issues since you would also need a remote interface for administering these services (MTS/COM+).

Just my .02