Yeah, I know about the 'Unload' button for isolated applications in a virtual directory (as per my first post to the originator of this thread). I went to the MSDN site and read-up on this but still couldn't get it to release the IIS app. I tried it on both IIS 4.0 and NTWS4.0 PWS but couldn't get it to work. Since I'm running DLL's and not EXE's on those virtual directories, they are running in the MTS. So, my I'm going to investigate shutting down the MTS package instead. Of course that doesn't necessarily help the EXE ones.

Yes, please post a solution here when you find it. I probably won't get around to my MTS searching for awhile.

>I got to playing with it last night too, and couldn't make it work the way I expected. I should have added- this is to unload an IIS application- that is, a virtual directory that has been specified to run in its own memory space. You can see the manual equivalent to this when you go to the properties for one of these virtual directories, and click the "Unload" button, which is supposed to release all processes running under that folder.
>
>I attributed my difficulties with my still basic understanding of IIS 5.0 running under Win2K server. The interface is somewhat different, and I couldn't get my applications to run in their own protected space. I'll be futzing with it more tonight. If I figure out how to do it, I'll post it here.
>
>
>
>>Thanks Erik. It didn't work for me but at least I've got a place to start researching it. I'm figuring I'll put the solution into my Project Hook beforebuild event to release the .dll just before building it.
>>
>>- A Hilton
>>
>>
>>>You should be able to use the IIS Admin objects through the ADSI interface (depending on the version if IIS: 4.0 or later)
>>>
>>>oIISFolder = GETOBJECT("IIS://LocalHost/W3SVC/1/ROOT/MyScripts")
>>>oIISFolder.AppUnload()
>>>
>>>
>>>This should release all out of proc applications in that folder...
>>>
>>>
>>>>Thanks Erik. So there's no way to use a batch file to do the equivalent of 'unload'ing that single virtual web directory? It has to be the net stop inetsrv for the entire web server? What about API calls? Right now I just do it manually but it gets tiresome.
>>>>
>>>>- A Hilton
>>>>
>>>>
>>>>>>If you run your website from a 'virtual directory' on the webserver then all you have to do is go to the properties for that virtual directory and hit the 'unload' button on the 'directory' tab. That'll release your VFP COM DLL so you can build a new version of the DLL. I thought I had read somewhere you could run a batch file with commands to do this automatically but it may have been just a dream. Anyway, it doesn't involve shutting down the entire web server.
>>>>>>
>>>>>
>>>>>The batch file approach does involve killing the service. It uses KILL.exe to kill the InetSrv service.