It's considered a best practice to sign assemblies with a Strong Name Key. While this has historically had issues, it's not actually the strong name signing that caused the issue attributed to it, and this viral problem only effects .NET Framework, which is now being deprecated.
As such, I'm all for going forward with this, as it opens the door to more consumers.
It's considered a best practice to sign assemblies with a Strong Name Key. While this has historically had issues, it's not actually the strong name signing that caused the issue attributed to it, and this viral problem only effects .NET Framework, which is now being deprecated.
As such, I'm all for going forward with this, as it opens the door to more consumers.