Com Callable Wrapper

[Roy Pereira]

I have the following problem:
I have a .NET component that I want to make callable
from COM enabled platforms (VB6, C++ 6.0, etc). However
this component makes use of another COM component (in this
case the AutoCAD COM interface). Acording to my
knowlegde, to create the CCW for a .NET Component, you
must generate a Strong Name Key. However, having done
that, I still can't get it to work as it prompts me for a
strong name key for the referenced COM library. Am I
doing this correctly? Please help.

[Huihong Luo]

All of its dependent assemblies MUST be strong named when you strong sign
one assembly. If you strong named assembly refers to an unmanaged COM, you
need to use TlbImp /keyfile:<filename> to generate a strong named assembly
from the Type library.

Hope this is helpful

Huihong
Decompiler, obfuscator and protector for.NET code
http://www.remotesoft.com
"Roy Pereira" <ro*********@rapistan.com> wrote in message
news:0a****************************@phx.gbl...

I have the following problem:
I have a .NET component that I want to make callable
from COM enabled platforms (VB6, C++ 6.0, etc). However
this component makes use of another COM component (in this
case the AutoCAD COM interface). Acording to my
knowlegde, to create the CCW for a .NET Component, you
must generate a Strong Name Key. However, having done
that, I still can't get it to work as it prompts me for a
strong name key for the referenced COM library. Am I
doing this correctly? Please help.

[Mattias Sjögren]

Roy,

Acording to my knowlegde, to create the CCW for a .NET Component, you
must generate a Strong Name Key.

No, an assembly doesn't need to be strong named to be registered with
COM.

Mattias

--
Mattias Sjögren [MVP] mattias @ mvps.org
http://www.msjogren.net/dotnet/
Please reply only to the newsgroup.