>>
>>So, the problem will be to register that component for our clients - I am wondering if I should use your RegisterDotNetComponent from the older article as is?
>>
>
>That's actually one of the big reasons I use wwDotNetBridge - I don't have to worry about registering it as a COM component. Plus I don't have to wrap every single method I want to use just to expose it via COM - I can call it directly.
>
>I just wrap something like this in a function or class:
>
>

>loBridge = CREATEOBJECT("wwDotNetBridge", "V4")
>IF loBridge.LoadAssembly(m.lcFullAssemblyPathAndName)
>   loObj = loBridge.CreateInstance("NameOfInstance")
>ELSE
>   * Error
>   ? loBridge.cErrorMsg
>ENDIF
>

Hmm, so you suggest to keep using the bridge, right? Ok, I'll remove the COM exposure from my library then.