A strongly-named assembly is required for DynamicExpresso.Core

[EvgeniyKom]

Hello! We are using your assembly through the Nuget package. Could you please sign your assemblies with a strong name, because it's imposible to use it from other strong named assembly.

Thanks!

[davideicardi]

Hello Evgeniy, currently I prefer to don't release a strongly signed assembly. Consider that this is an open source project, so if I strongly sign it then I should also put the key somewhere. Not in the source code otherwise the signing process doesn't make any sense (anyone can alter it...) and for now I prefer to keep the build process simple and just release a single version.

I suggest you to fork the project in a private repository that you can trust (or in a public repository but keep the key outside) and create a signed version of the assembly that you can guarantee, because only you have the key to rebuild.

In any case I will think about this requirement for the future...

thanks

[tongbong]

+1

It would be so nice to have a nuget package with a signed version of the assrmbly. What a burden to have to fork just to sign the assembly.

I do not like much signing as well but once an assembly is signed the signature chain has to be respected.

[tongbong]

Maybe this could help: https://github.com/anjdreas/UnitsNet/issues/262