Security and Localized Satellite Assemblies


This article applies to Visual Studio 2015. If you're looking for the latest Visual Studio documentation, use the version selector at the top left. We recommend upgrading to Visual Studio 2019. Download it here

If your main assembly uses strong naming, satellite assemblies must be signed with the same private key as the main assembly. If the public/private key pair does not match between the main and satellite assemblies, your resources will not be loaded. For more information on signing assemblies, see How to: Sign an Assembly with a Strong Name.

In general, you may need to have your organization's signing group or an external signing organization sign with the private key. This is due to the sensitive nature of the private key: access is often restricted to a few individuals. You can use delayed signing during development. For more information, see Delay Signing an Assembly.

See Also

Assembly Security Considerations
Key Security Concepts
Introduction to International Applications Based on the .NET Framework
Localizing Applications
Globalizing and Localizing Applications