You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Caution Do not rely on strong names for security. They provide a unique identity only.
and
If you are an open-source developer and you want the identity benefits of a strong-named assembly, consider checking in the private key associated with an assembly into your source control system.
There's no reason to keep the private key private. Doing so complicates local development and forces forks and private branches to create their own, incompatible key.
Originally opened by barnson
The text was updated successfully, but these errors were encountered:
Given https://msdn.microsoft.com/en-us/library/wd40t7ad.aspx:
and
There's no reason to keep the private key private. Doing so complicates local development and forces forks and private branches to create their own, incompatible key.
The text was updated successfully, but these errors were encountered: