Closed nareddykrishna closed 1 year ago
Yes that is correct, I dropped signing a few version ago because almost nobody uses strong names anymore and when using strong names yourself that gives trouble with finding nuget packages to do.
By any chance can I get signed copy of it?
Or what is last version which was signed?
Thanks Krishna Mohan Reddy Nareddy
From: Kees @.> Sent: Saturday, October 21, 2023 1:18:10 AM To: Sicos1977/MSGReader @.> Cc: nareddykrishna @.>; Author @.> Subject: Re: [Sicos1977/MSGReader] MSGReader version 5.4.5 not signed by SN (Issue #376)
Yes that is correct, I dropped signing a few version ago because almost nobody uses strong names anymore and when using strong names yourself that gives trouble with finding nuget packages to do.
— Reply to this email directly, view it on GitHubhttps://github.com/Sicos1977/MSGReader/issues/376#issuecomment-1773689770, or unsubscribehttps://github.com/notifications/unsubscribe-auth/BC5LDBZJJQADKGKVQSXRWPTYANSKFAVCNFSM6AAAAAA6JQXFI6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONZTGY4DSNZXGA. You are receiving this because you authored the thread.Message ID: @.***>
There are tools to sign an assembly when it is not signed but you then probably get issues with other packages that are referenced in MSGReader that are also not signed. The best is just to drop support in your app for signing.
If you ever are going to move away from the .net framework then there isn't a thing any more like strong naming an assembly
MSGReader version 5.4.5 not signed by SN