EBuild supports .NET Standard 1.6?

Upgrading in fact may be challenging - that Win 7 box is a shared build machine with quite conservative update policy. I can try setting up a clone locally, but it will take some time.

Let’s try to approach it from a different perspective: is there a way to tell EBuild which runtime to load (or run EBuild against a specific runtime)? It might be that we can get away with copying .NET 4.7 to some local directory and running EBuild against it.

I don’t think different (v4+) .NET runtimes cxamn co-exist own the same machine. One option would be to install 4.0 in a clean VM or on a clean machine and see if the issue reproduces; if so, update to 4.7 and see if to goes away or stays?