By the way, although I don't generally use this since I have control over
machines that will use .NET components, there is an alternative to
installing the assembly in the GAC, and it's probably better for your
situation. You can register the component with a codebase path by using
regasm's /codebase switch. This tells applications precisely where to find
the assembly without reverting to app directory search or using the GAC.
This is a little less invasive and much more like traditional COM
"Alex K. Angelopoulos" <aka(at)mvps.org> wrote in message
> Regsvr32 only works on COM-based components; you need to use regasm. Also,
> for the assembly to be used by any COM client - and NOT just used by an
> application hosted in the same directory as the assembly is installed - it
> will need to be installed in the global assembly cache.
> "Steve Le Mon" <steve_lemon@xxxxxx> wrote in message
>> Hi Andrew
>> I've been there and its no help. The problem here is this is a hybrid
>> DLL. It's .NET with a COM Interface grafted onto it, and I'm wondering if
>> this just adds to the confusion.I've tried to re-register the steps with
>> regsvr but get a "DLLRegisterServer entry point was not found" I'm
>> guessing this is because its not fully COM, but as the DLL works with
>> early binding I didn't think much about it.
>> The question here is should I be using Regsvr or Regasm... but this
>> doesn't explain why it works with early binding and not late binding???
>> "Andrew Morton" <email@example.com> wrote in message