? How to strong name a 3rd Party Assembly ?

Tony Jones

I have a third party assembly that I need to strong name because the C#
project I'm referencing it in will be strong named.

Every time I compile my project I'm getting "Assembly generation failed --
Referenced assembly 'xxxxx' does not have a strong name".

The referenced assembly is a .NET assembly that does not have a strong name.
It there a way to strong name it? I DO NOT have the source code for the
referenced third party assembly.

Thanks.

Tony

Jul 21 '05 #1

Subscribe Post Reply

2490

Mattias Sjögren

Tony,

The referenced assembly is a .NET assembly that does not have a strong name.
It there a way to strong name it? I DO NOT have the source code for the
referenced third party assembly.

Have you tried contacting the vendor and ask them if they can provide
a strongly named assembly?

Mattias

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

Jul 21 '05 #2

Tony Jones

Yes, but they said that had "problems" strong-naming the component. I don't
know what problems they are talking about - but I'm looking into the issue.

Thanks!

TJ
"Mattias Sjögren" <ma********************@mvps.org> wrote in message
news:#r**************@TK2MSFTNGP10.phx.gbl...

Tony,
The referenced assembly is a .NET assembly that does not have a strong name.It there a way to strong name it? I DO NOT have the source code for the
referenced third party assembly.

Have you tried contacting the vendor and ask them if they can provide
a strongly named assembly?

Mattias

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

Jul 21 '05 #3

Sean Hederman

If you can convince them to put in the DelaySignAttribute, that would
reserve space in the assembly that you can use to sign it.

Other than that, your only real option is IL roundtripping which is a
pain...

"Tony Jones" <to*******@junk.hotmail.com> wrote in message
news:Of**************@TK2MSFTNGP11.phx.gbl...

Yes, but they said that had "problems" strong-naming the component. I
don't
know what problems they are talking about - but I'm looking into the
issue.

Thanks!

TJ
"Mattias Sjögren" <ma********************@mvps.org> wrote in message
news:#r**************@TK2MSFTNGP10.phx.gbl...
Tony,
>The referenced assembly is a .NET assembly that does not have a strong name. >It there a way to strong name it? I DO NOT have the source code for the
>referenced third party assembly.

Have you tried contacting the vendor and ask them if they can provide
a strongly named assembly?

Mattias

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

Jul 21 '05 #4

by: Tony Jones | last post by:

Can anyone think of a reason why a 3rd party vendor writing .NET components would NOT strong name their assemblies? What harm does adding a strong-name to assembly present - I would think none...

.NET Framework

Error -- Referenced assembly does not have a strong name.

by: Vishal - Auh | last post by:

Hi, I'm creating a Strong named assembly which has a reference to a third-party Assembly. When I try to compile my assembly, I receive the following error "Assembly generation Failed --...

.NET Framework

Non-strong named interop libraries Part 2

by: Razzie | last post by:

Hey all, I'm really going through a small hell right now - I've completely lost it :) I made a project, using two interop libraries from exchange (created them as in this msdn article:...

C# / C Sharp

Deployment / Security / Strong Names

by: Jimski | last post by:

Hi all, I am creating an assembly that will access a database to return record details. I need to deploy it to a 3rd Party and they will then be able to use the assembly in their code to...

C# / C Sharp

Strong Name Assembly Issue

by: Richard | last post by:

Hi, We would like our application to be signed and have a strong name. However our application references a 3rd party .dll that does not have a strong name and so when we compile we get the...