Debugging environment configuration of DLL in ASP introduction

Now three-tier development, with ASP and VB6.0, but now suffer from not finding the right way to debug their own written DLL file, the efficiency is very low.
I have used several methods:
1. Select Uninstall in IIS, then recompile with VB, overwriting the original DLL
2. Select a site in IIS you are debugging, stop, and then compile the overlay, then start, and then refresh the page in IE.
3. Execute regsvr32.exe-u file name at command line and compile overwrite refresh
But the above method does not always work, I use FrontPage to do ASP page when there is no problem, but Use InterDev always report DLL file is locked, cannot overwrite error. Sometimes turning InterDev off (or just turning off all the files that are being edited) can work, but not always.
I want to use InterDev to do development, more convenient, but can not find a better way.
This problem has been bothering me for a long time, I think we do component development have this confused
----------------------------------------------------------------
I tried the following method this afternoon. I don't know if I'm going to make jokes, but I really solved the problem.
And I feel good about myself this afternoon.
But what I'm using is. NET's development environment
Specifically as follows:
1. Install. NET, of course, this system is very expensive resources, installed after the ordinary machine will run very slowly, if your voluntary more nervous or give up this method. (later I found in FrontPage and under the InterDev can also be achieved, haha.) Don't complain, because my words and installed a. NET but found that there is not much use, but I used to fall in love with him. )
2. Create a folder that holds the DLL. Then our most "wonderful" place is reflected: Create a number of empty subfolders under this folder named from 01 to the number you want.
3. Start IIS Manager
4. Open the VB6 your project
5. Now if you want to debug, you can compile directly, and then arbitrarily specify a second step to create a folder, I think from 01 start.
You refresh the ASP page you are debugging, see? The content is already the new DLL file you wrote.
The above is only the first time after the boot debugging. I was in the process of debugging found a lot of mistakes, I always so careless? Oh, I hope you are not like this:
Now I need to modify the DLL, after the modification is done recompile, you find that you can not overwrite the DLL just now, because you have called this component in the page, he has been put into memory, write protection lock. You need to stop your site in the IIS Manager. If you are using. NET, you will find that this is feasible, but the other development environment is not necessarily the same as you think, now you create the second step of the folder will be useful, find one of the folders (it is 02 ...). ), put the new DLL here. Then start the site (don't let him reboot, too slow, the most concise way to do this is to select your site in IIS, press the top corner of the