Interop component with strong name

[Kimmo Laine]

Hi,

we are using COM server through interop, and would like to sign our assembly
with strong name. But when building, we get the following error: "Assembly
generation failed -- Referenced assembly 'Interop.MyComS erver' does not have
a strong name."

How can is sign my COM server with strong name?
thx

Kimmo Laine

[Peter Rilling]

1) Use the sn.exe program that is included with the SDK to generate a
public/private key file.
2) Reference the key file in the AssemblyInfo file with the AssemblyKeyFile
attribute.

That should do it.

"Kimmo Laine" <reply.to@newsg roup> wrote in message
news:eG******** ******@TK2MSFTN GP09.phx.gbl...

Hi,

we are using COM server through interop, and would like to sign our assembly with strong name. But when building, we get the following error: "Assembly
generation failed -- Referenced assembly 'Interop.MyComS erver' does not have a strong name."

How can is sign my COM server with strong name?
thx

Kimmo Laine

[Mohamoss]

Hi Kimmo
May be I didn't get you right but I think you have and old com that you are
calling form a .net assembly which the VS should do for you?? . any way ,
you have an assembly that you want to sign with a strong name . what you
should do is
Generate a key file using the utility sn.exe with the argument -k and a
name of a file .snk like sn k- myfile.snk
Then open you assemblyinfo file and add the location of the key to the tag
[assembly: AssemblyKeyFile ("the uri of you file")] then recompile.

Mohamed Mahfouz
MEA Developer Support Center
ITworx on behalf of Microsoft EMEA GTSC

[Kimmo Laine]

Hi Peter,

i did it, but the compiler can´t use it because the referenced COM server is
not signed with strong name. Is there a way to sign the server (not .NET
code) with strong name.

Kimmo Laine

"Peter Rilling" <pe***@nospam.r illing.net> wrote in message
news:OR******** ******@TK2MSFTN GP10.phx.gbl...

1) Use the sn.exe program that is included with the SDK to generate a
public/private key file.
2) Reference the key file in the AssemblyInfo file with the AssemblyKeyFile attribute.

That should do it.

"Kimmo Laine" <reply.to@newsg roup> wrote in message
news:eG******** ******@TK2MSFTN GP09.phx.gbl...

Hi,

we are using COM server through interop, and would like to sign our

assembly

with strong name. But when building, we get the following error: "Assembly generation failed -- Referenced assembly 'Interop.MyComS erver' does not

have

a strong name."

How can is sign my COM server with strong name?
thx

Kimmo Laine

[Kimmo Laine]

Hi Mohamed,

you get me right! I did generate the key file, but compiler cannot use it
because the old COM server is not signed. Is there a way to sign this old
server somehow or to tell the compiler to ignore it.

Kimmo Laine

"Mohamoss" <mo************ @egdsc.microsof t.com> wrote in message
news:NE******** ******@cpmsftng xa10.phx.gbl...

Hi Kimmo
May be I didn't get you right but I think you have and old com that you are calling form a .net assembly which the VS should do for you?? . any way ,
you have an assembly that you want to sign with a strong name . what you
should do is
Generate a key file using the utility sn.exe with the argument -k and a
name of a file .snk like sn k- myfile.snk
Then open you assemblyinfo file and add the location of the key to the tag
[assembly: AssemblyKeyFile ("the uri of you file")] then recompile.

Mohamed Mahfouz
MEA Developer Support Center
ITworx on behalf of Microsoft EMEA GTSC

[Nicholas Paldino [.NET/C# MVP]]

Kimmo,

As indicated in other posts, you need to create a strong name using the
SN.EXE utility. However, you can not sign the COM assembly. The compiler
error is being raised because the interop assembly itself is not signed.
Instead of setting a reference to the COM component in your project through
VS.NET, you will have to run TLBIMP.EXE on the DLL that you want to use in
your program. When you run it, you can sign it using the /keyfile switch
(pointing to the output of SN.EXE). Once you have done that, set a
reference to that in your project in VS, and then compile. It should
compile fine.

Hope this helps.
--
- Nicholas Paldino [.NET/C# MVP]
- mv*@spam.guard. caspershouse.co m

"Kimmo Laine" <reply.to@newsg roup> wrote in message
news:eG******** ******@TK2MSFTN GP09.phx.gbl...

Hi,

we are using COM server through interop, and would like to sign our assembly with strong name. But when building, we get the following error: "Assembly
generation failed -- Referenced assembly 'Interop.MyComS erver' does not have a strong name."

How can is sign my COM server with strong name?
thx

Kimmo Laine

[Peter Rilling]

If that is the problem, then Kimmo could also set the "Wrapper Assembly Key
File" property in the property dialog for the project to sign those interop
assemblies, right?

"Nicholas Paldino [.NET/C# MVP]" <mv*@spam.guard .caspershouse.c om> wrote in
message news:ex******** ******@TK2MSFTN GP10.phx.gbl...

Kimmo,

As indicated in other posts, you need to create a strong name using the SN.EXE utility. However, you can not sign the COM assembly. The compiler
error is being raised because the interop assembly itself is not signed.
Instead of setting a reference to the COM component in your project through VS.NET, you will have to run TLBIMP.EXE on the DLL that you want to use in
your program. When you run it, you can sign it using the /keyfile switch
(pointing to the output of SN.EXE). Once you have done that, set a
reference to that in your project in VS, and then compile. It should
compile fine.

Hope this helps.
--
- Nicholas Paldino [.NET/C# MVP]
- mv*@spam.guard. caspershouse.co m

"Kimmo Laine" <reply.to@newsg roup> wrote in message
news:eG******** ******@TK2MSFTN GP09.phx.gbl...

Hi,

we are using COM server through interop, and would like to sign our

assembly

with strong name. But when building, we get the following error: "Assembly generation failed -- Referenced assembly 'Interop.MyComS erver' does not

have

a strong name."

How can is sign my COM server with strong name?
thx

Kimmo Laine