Something like that only that code would probably be in a vfp .exe that you execute on the server but kick off remotely. That is, unless there's a better way to do this from the IIS MMC in a distributed environment - I haven't really looked into this...
>Claude,
>
>If I understand you correctly I could issue some like the following in the VFP command Window:
>
>

>DirObj=GetObject("IIS://www.somedomain.com/W3SVC/1/Root/myvirtual")
>DirObj.AppUnload

>
>Then I could FTP a new MTDLL to the site and the next request would use the new DLL.
>
>
>>Simon,
>>all's that would have to be run remotely is the following:

>>DirObj=GetObject("IIS://LocalHost/W3SVC/1/Root/"+JustStem(cOutputName))
>>DirObj.AppUnload

>>where 'JustStem(cOutputName)' is the name of the virtual directory.
>>This is also what can be run from the project hook...
>>>Hi Claude
>>>
>>>You mentioned on the Web-Connect messageboard that you unload MTDLLs all the time that were in the High (Isolated mode). I am assuming you use the unload button in the Management Console. Can you automated this process so that you could unload the MTDLL at a remote site and update it with a newer version?
>>>
>>>Simon