Rick,

I noticed this am that my dev machine was serving pages even though I did not have it running. I then realized that there was an orphaned exe running. I have seen my exe hang and have to be killed to terminate, but I have not seen my exe run in COM when wc.ini is in file mode. I stopped IIS and it was there. I wondered if the latest wc.dll allows this to happen?

Orphaned EXE can happen in COM mode if the server crashes hard (ie. doesn't shut down properly). Since servers are out of process they won't go away when the Application Pool exe goes down.

It's not common, but then you're running wc.dll too which is generally not as reliable as the newer .NET component (for a number of reasons).

You can kill those on the Module Administration page - if file mode, unload servers will kill all EXEs file based or COM that might still be running.

+++ Rick ---