Strong name signature could not be verified

[bradymholt]

Strong name signature could not be verified

[bweber]

I am getting the same error. Downgraded and things work again.

[bradymholt]

@systemutvecklare or @bweber can you tell me:

1. What .NET flavor is your app targeting (.NET Framework v?, .NET Core, .NET Standard?)
2. Are you building in release mode?
3. Is your app strongly signed?
4. Is your app delay signed?

Thanks.

[jafin]

@bradyholt Same Issue.

1. .NET 4.6 (Net standard 1.1?)
2. Debug Mode
3. Not strongly signed
4. Not delayed signed

Reverting to 1.21.2 resolves error.

[Atrejoe]

Same Issue:

1..NET 4.6.1
2.Both in Debug Mode as Release Mode
3.Not strongly signed
4.Not delayed signed

Reverting to 1.21.2 resolves error.

Possibly related: after upgrading, maybe due to the netstandard requirement, I received a bunch of warnings regarding assembly bindings.
The suggestion is that the 53 assembly bindings should be made to map
C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\.NETFramework\v4.6.1\Facades\....dll (some version)
to:
C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\MSBuild\Microsoft\Microsoft.NET.Build.Extensions\\net461\ref\....dll (some later version)

Adding these assembly redirects does not fix the issue.

[bweber]

@bradyholt

1. .NET 4.6.2
2. Both Debug/Release modes
3. Not strongly signed
4. Not delayed signed

Reverting resolves the issue.

This library is used as part of Hangfire (https://www.hangfire.io/) and when upgrading Hangfire, we had pulled down the latest version of this library.

[bradymholt]

Can one of you that is having the problem try to install the package in a new app and see if it works? I'm think it might have something to do with the upgrade scenario only.

[bradymholt]

Also, I have a a pre-release version that removes signing that I'm hoping one of you could try. 2.0.1-beta1 https://www.nuget.org/packages/CronExpressionDescriptor/2.0.1-beta1 . Please let me know if it fixes the issue.

[jafin]

@bradyholt, I upgraded to the beta 2.0.1-beta1 and had no issues with strong name signature verification errors.

[bradymholt]

@systemutvecklare @bweber @jafin @Atrejoe Thanks for the help with this. I just published 2.0.1 which should fix the issue you are seeing.