Strong Name Assembly Issue

[Richard]

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 dreaded compiler error:

Assembly generation failed -- Referenced assembly 'Xxxxxxxxx' does not have
a strong name

Is there any way - perhaps with attributes - that my strong named assembly
can reference the unsigned 3rd party .dll? I think I know the answer to this
question {aka you can't} but I am asking anyway...

[Lenard Gunda]

Hi,

Actually, you cannot do that. It would make the whole strong name thing much
weaker if it allowed such a thing.

Is it impossible to get a strong named version of the 3rd party .dll?

Or if it would happen to be a COM Interop assembly, you might want to check
out:
http://support.microsoft.com/Default.aspx?kbid=313666
Regards
-Lenard

"Richard" <Ri*****@discussions.microsoft.com> wrote in message
news:42**********************************@microsof t.com...

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 dreaded compiler error:

Assembly generation failed -- Referenced assembly 'Xxxxxxxxx' does not
have
a strong name

Is there any way - perhaps with attributes - that my strong named assembly
can reference the unsigned 3rd party .dll? I think I know the answer to
this
question {aka you can't} but I am asking anyway...

[Richard]

"Lenard Gunda" wrote:

Is it impossible to get a strong named version of the 3rd party .dll?

The issue is that our application is supposed to be HIPAA {Health
Information Privacy Act} compliant. And after I was the one to push for
strong naming in a HIPAA compliant situation now I've shot myself in the
foot...

Referenced assembly is not COM; it's a 3rd party tablet support library
package. Probably is impossible to get a signed version of code; but we have
contacted them to see if they will help...

Also, we didn't really WANT to recompile the Enterprise Library but as -for
obvious reasons- it is not signed we had to do that too... Yukkk...

[Lenard Gunda]

"Richard" <Ri*****@discussions.microsoft.com> wrote in message
news:AE**********************************@microsof t.com...

Also, we didn't really WANT to recompile the Enterprise Library but
as -for
obvious reasons- it is not signed we had to do that too... Yukkk...

You don't actually need to recompile an assembly to sign. As far as I know,
AL.EXE can be used to sign after it has been compiled. You can alternatively
also use the attributes.

Take a look at the AL.EXE command line arguments (/keyfile)!
http://msdn.microsoft.com/library/de...ilityAlexe.asp

Also, here you can read more about signing:
http://msdn.microsoft.com/library/de...StrongName.asp

-Lenard