Add strong key

I have test project which is strongly signed. I know that having testing project strongly signed is stupid, but we have many of these and hope published ExpressionToCodeLib to be signed either.

Error	CS8002	Referenced assembly 'ExpressionToCodeLib, Version=2.5.1.0, Culture=neutral, PublicKeyToken=null' does not have a strong name.

[SimonCropp]

the only reason to SN a test-helping lib, is because a test project is testing a SN’d project, and that target project exposes [InternalsVisibleTo] so non public member can be tested. So in this case all libs the test project pulls in need to be SN’d

Having said that. in most real cases where i have seen this:

• the target project is an application, and not consumed as a lib by other projects, so internals are redundant and the project can just make those types public so they can be tested. project should just make those internal members public
• the project is using SN for security despite the doco saying https://docs.microsoft.com/en-us/dotnet/framework/app-domains/strong-named-assemblies

Do not rely on strong names for security. They provide a unique identity only.

[EamonNerbonne]

I though users can use StrongNameSigner regardless of what the nuget packages do? But I get that it would be convenient for them…