Recompiling asp VB Components with PWSBy Doug Dean
If you have been surprised when Visual Basic will not allow you to recompile a DLL after testing it out in an asp file, your not alone. Ah you say to yourself, stopping pws through the Personal Web Manager should do the trick. But alas, your VB only returns a 'Permission Denied' window. Shutting down the system and restarting works, but who could develop under these conditions?
There are better ways, especially with Visual Basic 6.
VB5 Component Recompiling - WIN98
If you're developing with VB5 and Windows 98, you can effectively stop pws with the following command line statement:
You can run this from the Start/Run menu. Or better still, place this line in a text file, save it, and create a desktop shortcut icon for easy clicking. After running this command line, your VB becomes friendly again and allows you to reco mpile your DLL.
To startup pws again, run the following statement in the same manner:
VB5 Component Recompiling - NT
If you're running NT the above solution won't work, but this will:
net stop iisadmin
net start w3svc
VB6 Component Recompiling
A new option in VB6 allows for the best solution so far - relatively speaking. VB6 allows you to indicate which asp file hosts your VB component. It then loads this asp host file whenever you run your component (note, that is run your component, as in the Run/Start menu option). In fact, if you run your component without first indicating your asp host file's name, the Project Property window will conveniently appear for you to do just that.
You can also get to the Project Properties window through the following menu selections: Project/Properties/Debugging. On the bottom half of the window there is a text-input field labeled 'Start browser with URL'. Place the full path of your asp host file that contains your component in this text-field. Click 'OK'.
Now instead of making a file DLL, simply run your VB program. Presto! Your asp file pops up revealing the results of your component's changes. Worth the price of upgrading from VB5 if you haven't done so yet!