Menu
What are the advantages of using strong named assemblies?
What are the things that can't be done with a normal assembly?
896
You should strong name your open-source . NET libraries. Strong naming an assembly ensures the most people can use it, and strict assembly loading only affects . NET Framework.
Signing an assembly with a strong name ensures that its name is globally unique. Assemblies with the same strong name are expected to be identical. For example, if you intend to share Unity assemblies among several applications, you can install them into the global assembly cache.
You can use the Strong Name tool to determine if the assembly is strongly named. In command prompt you can do this to verify it is a strong named assembly. You can also use Reflector or ILSpy to find the public key token.
Strong Key is a naming convention used in computer programming. There can be more than one component (e.g.: DLL) with the same naming, but with different versions. This can lead to many conflicts. A Strong Key (also called SN Key or Strong Name) is used in the Microsoft . NET Framework to uniquely identify a component.
Let me list the benefits of strong naming your assembly first:
Strong naming your assembly allows you to include your assembly into the Global Assembly Cache (GAC). Thus it allows you to share it among multiple applications.
Strong naming guarantees a unique name for that assembly. Thus no one else can use the same assembly name.
Strong name protect the version lineage of an assembly. A strong name can ensure that no one is able to produce a subsequent version of your assembly. Application users are ensured that a version of the assembly they are loading come from the same publisher that created the version the application was built with.
More on strong naming from Microsoft is in Strong-Named Assemblies (MSDN).
137
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
