>>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.
>>
>
>
>Ok, I've done some research (I guess, just cuz I like you), but I no longer


Ahhhh, gee Erik. I like you too. <g> And BECAUSE I like you as much as you like me (isn't it getting that warm-and-fuzzy feeling in the UT these days? LOL) I'll tell you about my research after reading your post here. I found a section called "Microsoft Transaction Server for Visual FoxPro Developers" in my MSDN that has (near the bottom) what I'm looking for "Using Visual FoxPro 6.0 Project Hooks". Quoting from it ....

"The MTS samples posted along with this document contain a special Project Hook class designed specially for MTS. This class automatically shuts down and refreshes MTS registered servers contained in that project. One of the issues that developers must consider when coding and testing servers under MTS is repeatedly opening the MTS Explorer to manually shut down processes so that servers can be rebuilt and overwritten. "

I haven't tested it yet. Although I don't know how relavent this is to WIN2K and it's use of COM+, I figured I would at least let others who might be reading this be aware of the article. Thanks again Erik for giving me some leads!



>have a NT 4 box with MTS to play around on (all my dev machines are Win2K now- In Windows 2000, there is no MTS, because transactions are built into COM+).
>There are a set of MTS admin objects that you can automate to set up and administer packages, and wouldn't you know it, one of them allows you to ShutDown a package...
>
>oCatalog = CreateObject("MTSAdmin.Catalog")
>oPackages = oCatalog.GetCollection("Packages")
>oUTil = oPackages.GetUtilInterface()
>
>oUTil.ShutDownPackage(cPackageID)
>
>cPackageID is obtained from the id property of one of the packages in your oPackages collection. It also has a name property that will allow you to identify which package is yours.
>
>I got all this from October MSDN...