"Henning Krause [MVP - Exchange]" wrote:

> Hello,
>
> in case of the OpenNetCf, you can't... you must get the source and compile
> it yourself. The OpenNetCF source is available, AFAIK.
>
> Are you sure you want to do the actual signing process later? This ist what
> your AssemblyDelaySign(true) implies. If you just want to sign your code,
> set it to false.
>
> Greetings,
> Henning Krause
>
> "Robert W." <RobertW@discussions.microsoft.com> wrote in message
> news:8A03160C-45E9-4B8C-ACFB-9FDA69FE35E8@microsoft.com...
> > I'm trying to sign my Visual Studio 2003 C#.net WinForms app. I'm
> > following
> > this article:
> > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnnetsec/html/strongNames.asp
> >
> > I've generated the public and public/private key files. Then I added the
> > appropriate lines in 'AssemblyInfo.cs':
> >
> > [assembly: AssemblyDelaySign(true)]
> > [assembly: AssemblyKeyFile("..\\..\\..\\publickey.snk")]
> >
> > I put these lines into my main EXE, plus two DLLs it references. One of
> > them compiles fine but the other one references
> > "OpenNETCF.Desktop.Communication", which is a 3rd party DLL.
> >
> > In this latter case, I'm receiving this error:
> >
> > Assembly generation failed -- Referenced assembly
> > 'OpenNETCF.Desktop.Communication' does not have a strong name
> >
> >
> > Since I don't produce this file, how do I give it a strong name?
> >
> >
> > --
> > Robert W.
> > Vancouver, BC
> > www.mwtech.com
> >
>