[lnkForumImage]
TotalShareware - Download Free Software
Confronta i prezzi di migliaia di prodotti.
Asp Forum
 Home | Login | Register | Search 


 

Forums >

microsoft.public.dotnet.framework.sdk

delay signing

Tom

10/15/2003 3:35:00 PM

Assuming that I use delaysigning for my assmebly, do I have to link the
application that uses this assembly after it is signed with a private/public
key par? Or is it enough to link the app when the app is signed with the
public key

Thanks.
3 Answers

David Levine

10/17/2003 1:45:00 AM

0

It is enough to link the app with the referenced assembly has been delay
signed with the public key. The purpose of delay signing is that you can
develop and write your code with only the public key in the referenced
assembly. As long as the referenced assembly has the public key token in it
you can link to it with other assemblies. If you look in the manifest of the
assemblies that have references to it you will see that they use a token to
the public key, not the private key. However, since the referenced assembly
does not have the cryptographic signature necessary for verification to
succeed you will need to configure your development/test machines to skip
verification of that assembly. See the docs for sn.exe for the command line
switches.

"Tom" <tom@hotmail.com.what> wrote in message
news:OK3rEs$kDHA.2732@TK2MSFTNGP11.phx.gbl...
> Assuming that I use delaysigning for my assmebly, do I have to link the
> application that uses this assembly after it is signed with a
private/public
> key par? Or is it enough to link the app when the app is signed with the
> public key
>
> Thanks.
>
>

Tom

10/17/2003 1:51:00 PM

0

Thanks Dave. The question is do I have to rebuild the application that
references the assembly after the assembly is signed with a private key
right before the product release. I had already compiled my application
after signing the assembly with public key.

Thanks for your help

Tom.

"Dave" <noSpamdlevineNNTP2@wi.rr.com> wrote in message
news:%23QmneAFlDHA.2000@TK2MSFTNGP12.phx.gbl...
> It is enough to link the app with the referenced assembly has been delay
> signed with the public key. The purpose of delay signing is that you can
> develop and write your code with only the public key in the referenced
> assembly. As long as the referenced assembly has the public key token in
it
> you can link to it with other assemblies. If you look in the manifest of
the
> assemblies that have references to it you will see that they use a token
to
> the public key, not the private key. However, since the referenced
assembly
> does not have the cryptographic signature necessary for verification to
> succeed you will need to configure your development/test machines to skip
> verification of that assembly. See the docs for sn.exe for the command
line
> switches.
>
> "Tom" <tom@hotmail.com.what> wrote in message
> news:OK3rEs$kDHA.2732@TK2MSFTNGP11.phx.gbl...
> > Assuming that I use delaysigning for my assmebly, do I have to link the
> > application that uses this assembly after it is signed with a
> private/public
> > key par? Or is it enough to link the app when the app is signed with the
> > public key
> >
> > Thanks.
> >
> >
>
>

David Levine

10/17/2003 8:50:00 PM

0

You shouldn't have to.

"Tom" <tom@hotmail.com.what> wrote in message
news:eBISbWLlDHA.2536@tk2msftngp13.phx.gbl...
> Thanks Dave. The question is do I have to rebuild the application that
> references the assembly after the assembly is signed with a private key
> right before the product release. I had already compiled my application
> after signing the assembly with public key.
>
> Thanks for your help
>
> Tom.
>
> "Dave" <noSpamdlevineNNTP2@wi.rr.com> wrote in message
> news:%23QmneAFlDHA.2000@TK2MSFTNGP12.phx.gbl...
> > It is enough to link the app with the referenced assembly has been delay
> > signed with the public key. The purpose of delay signing is that you can
> > develop and write your code with only the public key in the referenced
> > assembly. As long as the referenced assembly has the public key token in
> it
> > you can link to it with other assemblies. If you look in the manifest of
> the
> > assemblies that have references to it you will see that they use a token
> to
> > the public key, not the private key. However, since the referenced
> assembly
> > does not have the cryptographic signature necessary for verification to
> > succeed you will need to configure your development/test machines to
skip
> > verification of that assembly. See the docs for sn.exe for the command
> line
> > switches.
> >
> > "Tom" <tom@hotmail.com.what> wrote in message
> > news:OK3rEs$kDHA.2732@TK2MSFTNGP11.phx.gbl...
> > > Assuming that I use delaysigning for my assmebly, do I have to link
the
> > > application that uses this assembly after it is signed with a
> > private/public
> > > key par? Or is it enough to link the app when the app is signed with
the
> > > public key
> > >
> > > Thanks.
> > >
> > >
> >
> >
>
>