>We just hand-coded it.
>
>One thing that we have used is a DLL that is part of the Setup wizard. It's called VB5STKIT.DLL. It has a function to register DLLs in it. You can get the calls to reference it from the Setup source code the MS provides with VB.
>
>Another way, is to just declare a function with the desired DLL. Each ActiveX DLL (by definition) has 2 entry points. One, is DLLRegisterServer and the other is, remarkably, DLLUnregisterServer.
>
>So, if you can access the windows API from an ASP page, and I'm not sure you can, then you could just make the calls. Otherwise, you can create an ActiveX DLL that would do this for you, and you would just instantiate the object from that DLL, and call a method passing a dll filename.
>
>Let me know if I'm not making sense, and I'll walk you through it more slowly.

Well, it doesn't have to be an ASP. From the Web, I can fire a Visual FoxPro process which will do the API stuff. The difficult part is to code it. Do you know where is located the Setup source code?

But, I'm not sure we can do that if it is going thru MTS. I think we have to release the object from MTS first.