Closed LazyLeecher closed 2 years ago
Sure, we can look into it.
Since strong naming only offers identity and NOT code integrity, plus nowaydays this practice seems like it's being discouraged or not even used ("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."
), why do you need it? I'm simply curious.
Hi all,
Thanks for the project, I use a lot. But recently I need a version with SN and the FastCrud doesn't have one, can you guys compile a new project with SN on nuget like Dapper did, or include in your main project?
Thanks.