[Updated] .NET Framework app crashes at runtime when referencing a .NET Standard library

[cartermp]

F# applications cannot run on 15.6 Preview 3:

To repro:
ConsoleApplication18.zip

Using the above project, ctrl-f5.

Old issue

System.IO.FileLoadException: Could not load file or assembly 'FSharp.Core, Version=4.4.3.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. Strong name validation failed. 

https://www.nuget.org/packages/FSharp.Core/

What's going on here?

[btrepp]

System.IO.FileLoadException: Could not load file or assembly 'FSharp.Core, Version=4.4.3.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. Strong name validation failed. (Exception from HRESULT: 0x8013141A) ---> System.Security.SecurityException: Strong name validation failed. (Exception from HRESULT: 0x8013141A)

[forki]

yes same here. reverting paket upgrade.

[dsyme]

After being notified about this and after reviewing the above I decided to unlist the package https://www.nuget.org/packages/FSharp.Core/4.3.0.

"The package has been unlisted. It may take several hours for this change to propagate through our system."

[KevinRansom]

Ouch!!!!

It turns out that we started creating the nuget packages before we sign the assemblies in them. @brettfo and I will see what we need to do to fix that.

This was missed because sn-Vr is still in widespread use, curses ... and ... dotnet cli doesn't really care about the signing hashes.

Sorry for the inconvenience, we will address it quickly.

Kevin

[forki]

On the bright side: this was caught quickly after release. Also it's nice that a netstandard 2 version is coming. Am 25.01.2018 19:51 schrieb "Kevin Ransom (msft)" <notifications@github.com

…

: Ouch!!!! It turns out that we started creating the nuget packages before we sign the assemblies in them. @brettfo <https://github.com/brettfo> and I will see what we need to do to fix that. This was missed because sn-Vr is still in widespread use, curses ... and ... dotnet cli doesn't really care about the signing hashes. Sorry for the inconvenience, we will address it quickly. Kevin — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#4263 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AADgNEVR6U6ZDyYllPk9V1cU-pwwz6jAks5tOM0TgaJpZM4RsbRC> .

[KevinRansom]

Okay ... pushed 4.3.1 to nuget with signed binaries.

@forki, The serialization issue was a compiler bug, that is now fixed and does not require a netstandard 2.0 build. The fix should be shipped in the next preview.

[forki]

But there was a change in dependencies in the nuspec that looked like you shipped 2.0 support. Am 25.01.2018 23:10 schrieb "Kevin Ransom (msft)" <notifications@github.com

:

Okay ... pushed 4.3.1 to nugget with signed binaries. @forki <https://github.com/forki>, The serialization issue was a compiler bug, that is now fixed and does *not require* a netstandard 2.0 build. Should be shipped in the next. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#4263 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AADgNNNKKzrLXudM6r_Jx6hREzkPKeCWks5tOPvFgaJpZM4RsbRC> .

[forki]

Ok where is the difference between 4.3.1 package and 4.3.2 package?

[forki]

This seems to be fixed. (At least our build is now green again) Thank you very much!

[cartermp]

Closing as the immediate issue is fixed. Linking #4269 as the long-term solution