Satellite assemblies and strong name
Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance
Date: Thu, 12 Feb 2004 15:28:18 -0500
All -
I read out on MSDN that "If your main assembly uses strong naming, satellite
assemblies must be signed with the same private key as the main assembly."
Well if you allow the regeneration of resources at client sites, this forces
you to have to ship your strong name also.
Anyone know any workarounds for this.
ice
Relevant Pages
- Re: Custom security permission exception error message
... > We're planning to use strong naming for our app and this does indeed ... unrestricted permission grant. ... AllowPartiallyTrustedCallersAttribute (APTCA) to your library assembly. ... appropriate security audit of the target library assemblies since applying ... (microsoft.public.dotnet.security) - Re: strong name and web service
... Great, that solves one question, strong name won't be checked by clients. ... I am investigating the use of strong naming in our .Net solutions. ... What can I benefit from strong naming a web service? ... > You can assign a strong name to assemblies that make up a web service, ... (microsoft.public.dotnet.security) - RE: ASP.Net 1.1 shadow copy + reflection problem
... Well if you use strong naming the problem will not dissapear but rather ... If you load all your dll's from the same folder you can simplify this by ... > (assemblies) from other directories that are not the bin. ... (microsoft.public.dotnet.framework) - Re: strong naming?
... Lack of strong naming means the runtime only has a version and path to load. ... There may be cached assemblies, ... reference different "versions" of the dll. ... (microsoft.public.dotnet.framework) - Re: strong name and web service
... should use strong naming. ... I can not think of any direct benefits from signing web service code. ... > I am investigating the use of strong naming in our .Net solutions. ... >> You can assign a strong name to assemblies that make up a web service, ... (microsoft.public.dotnet.security) |
|