>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.

I don't call SetComplete or SetAbort from the test component. Although I tried with both of them from another component and the unload of my dll was just as random as without them. Do I need to call either of these functions if I mark my component as "Does not support transactions" in MTS? (just for tests purposes, of course, because, in fact, we need transactions.)

At this moment I want to have a sure way to unload the dll, just to make my development environment easier and faster. (If the dll is hold by MTS/IIS, I cannot overwrite it, etc.)

>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...

This is something I don't understand. As far as I read until now, MTS creates the objects. Why do they "live" in IIS's process?

Why do I need to involve VFP here? The components are written in VC++.

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

Well, I'm not very sure MTS is usefull for this project. :) But my boss and other two members in the team want to use MTS really bad :) and it's not my decision right now. Our BOs must work in MTS and that's all. :) In the mean time, I understand that MTS makes things easier for transaction management. Is this wrong?

Vlad