Now I am engaged in three-layer development, use ASP and VB6.0, but now I haven't found a suitable method to debug your own DLL file, the efficiency is quite low.
I have used several ways: 1. Select uninstall in IIS, then recompile it with VB, override the original DLL2. Select a site you debug, stop, then compile, then start, then in IE refresh page. 3. Execute the regr32.exe -u file name in the command line and then compile override
However, the above method is not always getting effective, I have no problem when using FrontPage to do ASP pages, but always reporting the DLL file when using InterDev, and cannot overwrite errors. Sometimes turn the interdev (or just turning off all the edited files), you can also get the product, but not always. I want to develop in InterDev, more convenient, but I can't find a better way. This problem is troubled for for a long time, I think everyone has this confused.
-------------------------------------------------- ----------------
I tried the following this afternoon, I didn't know if I would make everyone joke, but I really solved the problem and I feel good today. However, I use .NET's development environment as follows: 1. Installation .NET, of course, this resource for the system is very costly, and the ordinary machine will run very slowly after installation, if your voluntary is more nervous or give up this method. (Later I found out under FrontPage and INTERDEV, haha. Don't complain, because my words are installed. Net I found out that there is not much used, but I have used it.) 2. Establishment A folder that stores DLL. Then our most "excellent" place is reflected: establish a few empty subfolders under this folder to start from 01 to the value you want. 3. Start IIS Manager 4. Open VB6 Your Project 5. Now if you want to debug, you can directly compile it, then specify a second step-building folder, I think it is starting with 01. You refreshed the ASP page you debugged, saw it? The content is already a new DLL file you wrote.
The above is just the first debugging after boot. I found a lot of mistakes in the process of debugging, I am always so big? Oh, I hope you are not like this :) Now I need to modify the DLL, recompile after the modification is completed, you find that you can't override the DLL just now, because you have called this component in the page, he has been put into memory Write protection locked. You need to stop your site in the IIS manager. If you use .Net, you will find that this is feasible, but other development environments do not necessarily with you, now you have established. Those folders will be used, find a folder (which is 02 ...), put the new DLL here. Then start the site (don't let him restart, too slow, the above steps are the simpler way to select your site, press █, then ▼) (I didn't find ▼, you can only put ▼ " Time-needle rotation 30 degrees read ^ _ ^)
how about it? The problem solved?
I recommend using .NET, because use it, you don't need to perform REFERENCE as the interdev, just directly write the extension name is the page of the ASP, then each object in the code is used to get the method of server.createObject (") method, He will automatically display the methods and properties of the class in the latest DLL you compile. If you don't want to use the codeInsight, I think FrontPage is also a good tool. Is my method is not very stupid?
I don't have to use vb.net or C # is because my current work is packaged code rather than renewing the difference between VBScript and .NET, I still choose this stupid method, and I think VB Write DLL maybe performance Will be better, isn't it?
