Architect.DomainModelling is not signed

[JoergHoffmannatGitHub]

The code-base that I am currently working with consists of a large set of binaries that are all signed. The savvy .NET devs out there will know that any assembly that’s used/referenced by a signed assembly must also be signed.

This is an issue when dealing with Architect.DomainModeling library that is not signed.

[Timovzl]

According to the docs: "For .NET Core and .NET 5+, strong-named assemblies do not provide material benefits. The runtime never validates the strong-name signature, nor does it use the strong-name for assembly binding."

That covers all versions that have ever been supported by this library.

What is the reason to use strong-named assemblies in the code base you are working on?

[JoergHoffmannatGitHub]

This is new to me. The forked project I'm continuing to work on was started in 2007 with .NET Framework 3.5 and used strong naming.
When I added a library, the compiler issued warning CS8002. So I added strong naming to the new library.
Now I know that I can omit strong naming since everything is .NET 8.0.

Thank you for this information.