Automatic strong-name signing of referenced assemblies.
Utility software to strong-name sign .NET assemblies, including assemblies you do not have the source code for.
If you strong-name sign your own projects you may have noticed that if you reference an unsigned third party assembly you get an...
This is targeted for signing the contents of NuGet packages that are using unsigned assemblies, in order to be able to link to these packages where the consuming project is strongly named. Access to the original source code is not required, and you may sign any assembly with your own strong naming...
Strong Namer will automatically add strong names to referenced assemblies which do not already have a strong name. This will allow you to reference and use NuGet packages with assemblies which are not strong named from your projects that do use a strong name. NOTE: This fork use MsBuild 12 instead...
This is an msbuild target that will try to create the key file that is used by the project it is installed to when it doesn't exist already.
Which is a well known problem for open source projects:
You do want to sign your assemblies, but you don't want to give away the key file.
Use Ixxat.Vci4 package to access CAN interfaces from Ixxat/HMS Networks via .NET and VCI4-API. This package provides strongly named assemblies and supports net40/net5.0-windows/net6.0-windows and netcoreapp3.1. Mixed assemblies depend on universal runtime (VCRUNTIME140.dll).