>>Regardless, though, that doesn't solve the update problem. With ASP/IIS
>>there's no way to update a COM object on a busy site without shutting
>>the site down. Now imagine if you have an app that consists of dozens
>>of separate COM DLLs... Won't that be fun? <s>
>
>Big fun! :) I was talking more about the development time, when one has to replace the dll every few minutes and the fact that the dll is hold by IIS/MTS is a real PITA.

There are several ways to deal with that. Build your component as an
EXE while developing. That way it unloads.

If I do test with DLL servers I usually run a batch file that unloads
and reloads the IIS service. Much quicker than clicking through the
various dialogs all the time. While the server stops and restars I can
rebuild the component.