root cause - Githubissues

Krzysztof-Cieslak / InteractiveFCS

0 stars 0 forks source link

root cause #1

Open baronfel opened 2 years ago

baronfel commented 2 years ago

dotnet.interactive loads older versions of the MSbuild dlls. here's a before-and-after:

before the load, you can see the 15.x libraries. after #r load, the same older versions are in place, despite projinfo needing 16.x versions.

baronfel commented 2 years ago

@jonsequitur here's what I found^ how does .net interactive manage dependencies? can notebooks have a dedicated appdomain or something?

jonsequitur commented 2 years ago

Currently there are no separated dependency load contexts. If an assembly is in .NET Interactive's dependency graph, then you can't load a different version. We would like to add this capability.

jonsequitur commented 2 years ago

I'm not seeing these assemblies in the latest version of .NET Interactive:

I'm wondering if we changed these dependencies since this issue was opened.

Krzysztof-Cieslak commented 2 years ago

Unfortunately, it seems I'm still getting the same MsBuild version conflict as before