.NET Core Assemblies strong naming


#1

Hello. Can anyone clarify to me if the verification of strong-named dependent assemblies is supported for .NET Core?

I created a simple solution consists of two .NET Core projects: console app and library - both are signed. Later in the binaries I replace library with one which is not signed, but application was still working.
But similar experiment with .NET Framework assemblies was successful: after library has been replaced, application fallse down with exception System.IO.FileLoadException as expected.


#2

I personally think that you must not sign your assemblies unless you have very strong arguments doing so.

Here are some resources:



http://james.newtonking.com/archive/2012/04/04/json-net-strong-naming-and-assembly-version-numbers


.NET Foundation Website | Blog | Projects | Code of Conduct