Closed codewerfer closed 1 year ago
Thanks for figuring this out. I guess I have to drop strong naming support then because Microsoft also stopped signed some of their packages. Signing is something of the past and I only added it because years ago it was the way to go. It probably is going to break old projects from people that require it but I see no other solution. I don't think Microsoft is going to sign their package when I ask for it :-)
Dropped support for signing
Creating a fresh new net47 Winforms App and add
MsgReader
as a Nuget from Nuget.org results in an Exception at Runtime. Assembly "Microsoft.Maui.Graphics, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null" ... not found. A strongly-named assembly is required. (HRESULT: 0x80131044)(edit: replaced with correct screenshot)
Using
Microsoft.Maui.Graphics
inside this App (for the same context used byMsgReader
likePlatformImage.FromStream(fs).Save(fs_out)
) works fine. (Therefore, theMicrosoft.Maui.Graphics
Assembly is there and can be accessed.)Build
MsgReader
(thx for your work) from source without signin and use this unsigned, not strongly named Assembly also works.It seems the use
Microsoft.Maui.Graphics
- which has no strong name - leads to problems when it is used as reference by a strongly named Assembly.