Could not load file or assembly or one of its dependencies. Reference assemblies should not be loaded for execution

[mh (marc hoffman)]

@JohnMoshakis

The “Child references” post is my latest, is the test case ok ?

It’s ok, but its also behaving “as designed”, not copying stuff from “lib/netstandard2.0”.

This is the current status quo:

@mh

that package as only a lib folder, and only for

netstandard1.0
netstandard1.1
netstandard2.0

I dont fall back to netstandard2.0 for lib , when building net4x anymore. if I change that, the original issue is broklen again, because System.Buffer has a lib folder for netstandard2.0 , and we’ll be deploying that version of the System.Buffer.dll again.

@mh

One last idea I have, would be to allow fallback on lib if and only if there was no ref folder at all. With that, both projects work (but i’m sure we’ll find a new one that fails). I’ll go ahead and commit that change and we’ll see what goes.

[JohnMoshakis]

Will this result in System.Buffers being copied to the debug folder ? A visual studio project referencing Microsoft.Bcl.AsyncInterfaces pulls in .net standard but hasnt got system.buffers.

[mh (marc hoffman)]

@JohnMoshakis

Will this result in System.Buffers being copied to the debug folder ? A visual studio project referencing Microsoft.Bcl.AsyncInterfaces pulls in .net standard but hasnt got system.buffers.

The fix to the above issue is what prevented System.Buffers from being copied, and its the same reason why System.Unsafe isn’t either in the other scenario.