You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Fake is used by fslab journal's build command. I have a journal that uses newtonsoft.json for deserialization. However no matter what I do to reference a desired version of the DLL, the fsjournal's build run command always insists to use the one that's in FAKE/tools/newtonsoft.json.dll, which targets .NET v40. This is the actual deserialization problem I run into. And can only be solved by having the newtonsoft.json.dll that targets .NET 4.5.
Here's my script that shows my reference to the DLL on the very first line.
// even if I specifically ask to load my desired DLL, the actually loaded one in FSLab journal uses the one
// in Fake/tools/newtonsoft.json.dll, which is older and buggy.
#r @"newtonsoft.json.9.0.1\net45\Newtonsoft.Json.dll"
#load "packages/FsLab/FsLab.fsx"
open Newtonsoft.Json
open Deedle
open System.Collections.Generic
(**
This will fail deserialization due to undesired Newtonsoft.Json.dll loaded
*)
let x = JsonConvert.DeserializeObject<IReadOnlyDictionary<string,string>>("""
{
"Something": "1.8",
"Something2": "0.10000000000000001",
"Something3": "answer3",
}""")
The text was updated successfully, but these errors were encountered:
Fake is used by fslab journal's
build
command. I have a journal that uses newtonsoft.json for deserialization. However no matter what I do to reference a desired version of the DLL, the fsjournal'sbuild run
command always insists to use the one that's inFAKE/tools/newtonsoft.json.dll
, which targets .NET v40. This is the actual deserialization problem I run into. And can only be solved by having the newtonsoft.json.dll that targets .NET 4.5.Here's my script that shows my reference to the DLL on the very first line.
The text was updated successfully, but these errors were encountered: