Are you calling SetComplete or SetAbort? If you don't call SetComplete
MTS won't release the object - it'll treat it just as if you had
a local reference.

IIS *never* releases any InProc servers. However, MTS should. Test it
from VFP to make sure that MTS is doing things right before messing
with IIS...

Why are you bothering with MTS anyway? Worthless for scalability...

+++ Rick ---


>I started to develop some business objects in VC++ as ATL-MTS-components. MTS+ISS run on my computer, ie: everything is locally.
>
>I set the idle unload timeout to 1 minute in MTS Manager, but MTS (or is it IIS in fact?) fails to unload the dll almost all the time (sometimes it does free it, but I couldn't find the pattern... yet:)).
>
>So, I thought I'm doing something wrong in my code and I created a new package that contains a dummy component as it is generated by the ATL wizard. The same problem: MTS does not free the dll.
>
>Until now, I have two solutions to force the unload of the dll (besides the complete reboot which is not a solution :)):
>
>1. Stop/restart the IIS service. I don't like it because it's still too long.
>2. Run the components in debug mode. This is not good because the debug is slower and I can't get the "feeling" on how things actually work.
>
>What am I missing here? Is there any other magical setting?
>
>Vlad