>We are developing a web site hosted in a shared environment and using some Visual Basic dlls. Whenever we need to make change, we have to do following,
>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.
>
>This sounds rediculus. We have to WAIT otherwise not able to overwrite the old dll.
>
>We must do know how to do it correctly. please help...

Can you provide more info on this? Do you have some VFP components at all or this is just some VB project with VB DLLs? From VFP, from the project manager, there is some ways to automate the update of such a DLL. We have discussed those issues last week, again, and that is fairly easy to do.