Closed lostromb closed 5 years ago
related to moving to new markdown lib. think I know how to fix things here :)
Oh goody, and I just realized I could also use the 1.2.0 nuget version which is signed correctly, so I'm not too terribly blocked by this anymore :-)
@paulcam206 does this mean we'll need to issue a patch to fix the signing for 1.2.1 binaries? Now that we have the new certs as well, let's target sometime today to republish?
just a heads up -- this fix should be shipping in 1.2.2 either today or Monday :)
:tada:AdaptiveCards@v1.2.2
has been released which incorporates this pull request.:tada:
Handy links:
Platform
What platform is your issue or question related to? (Delete other platforms).
Author or host
Host
Version of SDK
Nuget 1.2.1
Issue
I spent all day today struggling with an issue when loading the AdaptiveCards netstandard1.3 library into my project (indirectly, via a bunch of complicated Assembly.Load() / AppDomain stuff that is only semi-relevant). Every time, my program would fail at startup with the exception:
After much frustration I discovered that the netstandard1.3 dll was different from the other two in terms of strong name signing, in that it was only delay-signed but not "fully" validated. This is what was causing my runtime to fail to load them. Validating them manually with Sn.exe shows this:
Of course one option is to upgrade my project to one of the other runtimes, but my project is plugin-based and I'm trying to maintain the broadest level of compatability which is why I'd prefer to target the lower version. Would it be possible to fix this simple issue in the next release?