Re: Building satellite assemblies where the template is strong named

Tech-Archive recommends: Fix windows errors by optimizing your registry

From: Peter Singer (petes_at_knorrassociates.com)
Date: 04/27/04 

Date: Tue, 27 Apr 2004 15:45:21 -0400

Neither of these solves the problem. If I try and do an AL using the public
portion of the strongname it generates an error saying it needs the private
key as well. I don't see how Delayed Signing does anything for me as my
customers need to be able to build satellite assemblies and I'm not about to
give them our private key. Please advise.

"Tian Min Huang" <timhuang@online.microsoft.com> wrote in message
news:skL0hveJEHA.3800@cpmsftngxa10.phx.gbl...
> Hello,
>
> Thanks for your post. I reviewed your description carefully, and now I'd
> like to share the following infomration with you:
>
> 1. As I understand, your satellite assemblies need to reference a
> strong-named template assembly. If so, you customer just need to get the
> public key instead of private key. Please refer to the following MSDN
> articles:
>
> Referencing a Strong-Named Assembly
>
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpguide/htm
> l/cpconstrongnamescenario.asp
>
> Strong Name Scenario
>
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpguide/htm
> l/cpconstrongnamescenario.asp
>
> 2. If it is not the case, I strongly recommend you delay signing the
> assembly to work around the problem:
>
> Delay Signing an Assembly
>
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpguide/htm
> l/cpcondelayedsigningassembly.asp
>
> Hope this helps.
>
> Regards,
>
> HuangTM
> Microsoft Online Partner Support
> MCSE/MCSD
>
> Get Secure! -- www.microsoft.com/security
> This posting is provided "as is" with no warranties and confers no rights.
>

Relevant Pages

  • Re: Decompiler.NET reverse engineers your CLS compliant code
    ... If you could send the assembly to MSFT to get signed with their private key then only the public key woul dneed to ship with the CLR. ... > This shouldn't be a big problem, but since all assemblies will be ...
    (microsoft.public.dotnet.languages.csharp)
  • Re: Decompiler.NET reverse engineers your CLS compliant code
    ... If you could send the assembly to MSFT to get signed with their private key then only the public key woul dneed to ship with the CLR. ... > This shouldn't be a big problem, but since all assemblies will be ...
    (microsoft.public.dotnet.languages.vb)
  • Re: Decompiler.NET reverse engineers your CLS compliant code
    ... If you could send the assembly to MSFT to get signed with their private key then only the public key woul dneed to ship with the CLR. ... > This shouldn't be a big problem, but since all assemblies will be ...
    (microsoft.public.dotnet.languages.vc)
  • Re: Decompiler.NET reverse engineers your CLS compliant code
    ... If you could send the assembly to MSFT to get signed with their private key then only the public key woul dneed to ship with the CLR. ... > This shouldn't be a big problem, but since all assemblies will be ...
    (microsoft.public.dotnet.framework)
  • Re: Assembly.Load fails after assembly preloaded using Assembly.LoadFrom (v1.1.4322)
    ... "avoid LoadFrom as much as possible" is precisely due to issues like this. ... One reason why assemblies already loaded in the LoadFrom context aren't ... > of the same file I'd much rather use the GAC. ... > Create a child code group using strongname permission and import public ...
    (microsoft.public.dotnet.framework.clr)