Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
[Announcement] Assemblies are now strong named #3156
It was my impression that we were moving away from strong named assemblies. Or maybe I'm just mistaken. The fact that you have to validate an assembly while somebody already has access to your file system seemed a bit redundant.
Are those assemblies for backward compatibility only?
There are a number of reasons.
One reason we enabled strong naming is that we have cases where for a variety of reasons something that depends on the code here must be strong named, and so we must be strong named. (Strong naming is viral.)
Another reason (closely related to the first) is that in order to release critical security updates when running on .NET 4.x, we have to be able to install patches into the GAC, and the GAC requires strong naming.
As a hater of strong naming I feel your pain. (intensely)
There's a few things that alleviate the pain when using our new toolchain and runtime, and changes to the process:
It's disappointing that for .NET Framework, the problems all still exist but such is life...