>>That's where I get confused. What is the difference between setting application protection on virtual directory and putting DLL in a COM+ package? They both allow you to "unload" application without stopping web server. Do they both offer JIT?
>
>When you enable application protection, this basically means that IIS 5 creates your COM object in a separate EXE (DLLHOST.EXE). This is the same EXE that is used in COM+ Services (MTX.EXE was what MTS used). In fact, internally IIS creates a COM+ application for each virtual directory and adds a component for each directory with most COM+ features disabled.

Hi Christof,

Mind if I join the class? <g> What is the benefit of this approach over a VFP COM EXE (besides extra COM+ features)? If I understand correctly, under MTS, in-process DLLs are loaded into the already running MTS process, which enables that sort of thing and is relatively light. When using application protection, is a separate process created, or is the DLL hosted in the already running COM+ process? Please correct me if I'm on the wrong track.

BTW, I really enjoyed your article on threading, although I probably need to read it a few more times. You should give a DevCon session on it. Thanks.