I'm not sure this is the best way, but you can stop IIS and the just reregister the DLL.<BR><BR>If you don't want to stop IIS (and who does) just register the DLL with a new name, and change your code that calls on it.
This is the way i'm doing it now.<BR><BR>If i need to change the DLL, i stop IIS by the following command line:<BR><BR>net stop w3svc<BR><BR>Then I save the DLL with VB which registers it. and restart the server(dev machine)<BR><BR>net start w3svc<BR><BR>
If your using VB 6 if you go into the Project|Properties|Debugging and then go to the textbox start browser with URL, put any page on your site in here,VB6 runs it in the environment that is until you have to deploy.
<BR>the problem regarding the register / UnRegister is very usual in case of using dll for ASP. when the dll is referenced by any of the asp page it gets locked ... unless untill the IIS is stopped and start again it does not release it ... <BR>the best way is to use "Run the project from a browser with the url (.asp file ) .. it works perfectly ....<BR>the other way is very complicated . u need to change the IIS Settings for that ...<BR>in the properties menu from the web site go to the tab Home directory <BR>there are three buttons <BR>Remove, Configuration, Unload <BR>Click on Configuration and add your Dll in that .... when ever u want to update and reload the new Dll u just need to unload using the option given UNLOAD ....<BR>