Skip to content
This repository was archived by the owner on Apr 20, 2023. It is now read-only.

Conversation

@rainersigwald
Copy link
Member

This is a continuation of #8876 but I didn't have permissions to edit that. It picks up:

  • The new MSBuild with the workaround flag
  • A new NuGet required to take that
  • Opting into the workaround from dotnet test.

AndyGerlicher and others added 7 commits March 22, 2018 16:08
* Add feed to msbuild myget
* Update MSBuild to 15.7.108 (contains both netcoreapp2.0 and
netcoreapp2.1)
* Move some projects to netstandard2.0

* Use version agnostic $(TargetFrameworkIdentifier) property to make changing versions easier since we only care about .NET Framework vs .NET Standard
* Add missing project to solution file
* Update TestPackageProjects.targets to use netstandard2.0 on non-Windows
…explicit reference to netstandard 2.0 to TestFramework.
Work around microsoft/vstest#1503 by using the
MSBuild escape hatch variable MSBUILDENSURESTDOUTFORTASKPROCESSES and
ensuring that tests don't run in a disconnected MSBuild process by
passing /nr:false.
@livarcocc livarcocc merged commit ce4d914 into dotnet:release/2.1.2xx Mar 26, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants