search

Sicos1977 / TesseractOCR

A .net library to work with Google's Tesseract
169 stars 22 forks source link

Assemblies on NuGet are not Strongly Named #53

Closed kirk56k closed 6 months ago

kirk56k commented 9 months ago

I know this is a long shot, and I'll fork this and build it myself to fix this in the short term. But it would be awesome if you could Sign your assemblies so they are Strongly Named. My project must be signed for its use case, and thus all assemblies it uses must also be strongly named. I was moving from CharlesW's amazing C# wrapper for Tesseract to yours, since yours seems to be more currently maintained and seems to be more in-line with best practices. Thanks in advance either way!

https://learn.microsoft.com/en-us/dotnet/standard/assembly/sign-strong-name

Sicos1977 commented 6 months ago

I stopped signing libraries that I make because as soon as you start signing things youre whole dependency has to be signed...