Just my $0.02 on this problem, after one year of trying almost anything :)

If you want to be productive, forget about Win9x. Use NT with IIS. NT Workstation is good, NT Server is better.

The only method that works all the time to unload your dll is to kill the IIS process. You can do it by using KILL INETINFO in a DOS window (KILL.EXE is installed with Windows NT Resource Kit) or from the Control Panel/Services applet. Sometimes (rarely), the applet will lose control over IIS. KILL.EXE works all the time.

Regardless of whever you use IIS or not, Windows NT is much more reliable than 9x for development purposes (especially when your app crashes the system). I would say that NT is almost a must for any serious developer (mainly form the productivity point of view).

Vlad

>I am looking into implementing some VFP Automation servers, to be instantiated in ASP pages on our web site. Whenever I run an ASP page that creates an instance of a VFP automation server, the DLL is loaded into memory, and not unloaded when the server object is released on the asp page. This means that in order to modify the server in VFP, I have to re-boot my development machine to clear the DLL from memory. I am developing on my desktop machine using VFP 6 and personal web server. Once completed, the project will be moved to an IIS machine. I believe this problem has to do with the dll being cached by the web server, but I don't know how to unload it. I have made sure that the server object is released on the asp page, closed the browser to make sure the session is released, and stopped the WWW service on the Personal Web Server - but the DLL is still loaded. How can I unload this library so I can modify and recompile it?
>
>TIA
>Bill Sabo