Newtonsoft.Json 12.0.0 from dotnet-script always imported even when 13.0.1 package installed

[georgiosd]

This simple script:

#r "nuget: Newtonsoft.Json, 13.0.1"

Console.WriteLine(typeof(Newtonsoft.Json.JsonConvert).Assembly);
Console.WriteLine(typeof(Newtonsoft.Json.JsonConvert).Assembly.Location);

Prints:

Newtonsoft.Json, Version=12.0.0.0, Culture=neutral, PublicKeyToken=30ad4fe6b2a6aeed
C:\Users\georgiosd\.dotnet\tools\.store\dotnet-script\1.3.1\dotnet-script\1.3.1\tools\net6.0\any\Newtonsoft.Json.dll

😱

[filipw]

This is "expected". The few of own dependencies of dotnet-script are loaded into the same default assembly load context as the script. Since they are first, they win over the script ones.

You can suppress this behavior by adding the flag --isolated-load-context when running the script.

[georgiosd]

@filipw perhaps it would be prudent to issue a warning for this if there is a version mismatch, for the uninitiated souls?

[billlin0904]

How can i set flag --isolated-load-context in vscode launch.json?

[seesharper]

{
  "version": "0.2.0",
  "configurations": [
    {
      "name": ".NET Script Debug",
      "type": "coreclr",
      "request": "launch",
      "program": "${env:HOME}/.dotnet/tools/dotnet-script",
      "args": [
        "${file}",
        "--isolated-load-context"
      ],
      "windows": {
        "program": "${env:USERPROFILE}/.dotnet/tools/dotnet-script.exe",
      },
      "cwd": "${workspaceFolder}",
      "stopAtEntry": false,
    }
  ]
}