ExhaustiveMatching
ExhaustiveMatching copied to clipboard
Strong name the assembly
I had a nasty runtime error just now in a strong-named project targeting .NET Framework 4.8 that uses this NuGet package, as strong-named assemblies transitively require all referenced assemblies to also have strong-names.
I can work-around it with the StrongNamer
hack package, but I'd prefer it if this assembly were strong-named properly in the first place.
Microsoft explicitly recommend that libraries distributed as NuGet packages should be strong-named:
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.
I have added strong-naming in my branch here: https://github.com/daiplusplus/ExhaustiveMatching/tree/dev/2011-11-strong-naming
Because this branch builds off my current PR, I'll submit this as a PR once my existing PR is merged.