Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

vstest fails to build with the latest .NET 6.0 SDK #3044

Closed
MichaelSimons opened this issue Sep 8, 2021 · 0 comments · Fixed by #3077
Closed

vstest fails to build with the latest .NET 6.0 SDK #3044

MichaelSimons opened this issue Sep 8, 2021 · 0 comments · Fixed by #3077
Assignees
Labels

Comments

@MichaelSimons
Copy link
Member

MichaelSimons commented Sep 8, 2021

  /repos/tarball111/.dotnet/sdk/6.0.100-rc.2.21426.20/Sdks/Microsoft.NET.Sdk/targets/Microsoft.NET.EolTargetFrameworks.targets(28,5): warning NETSDK1138: The target framework 'netcoreapp2.1' is out of support and will not receive security updates in the future. Please refer to https://aka.ms/dotnet-core-support for more information about the support policy. [/repos/tarball111/src/vstest.e79909063ddfc9d8fd4959e072b2dcf5e8d9d3c1/artifacts/source-build/self/src/src/vstest.console/vstest.console.csproj]
  /repos/tarball111/src/vstest.e79909063ddfc9d8fd4959e072b2dcf5e8d9d3c1/artifacts/source-build/self/package-cache/microsoft.extensions.filesystemglobbing/6.0.0-dev.21457.6/buildTransitive/netcoreapp2.0/Microsoft.Extensions.FileSystemGlobbing.targets(4,5): error : Microsoft.Extensions.FileSystemGlobbing doesn't support netcoreapp2.1. Consider updating your TargetFramework to netcoreapp3.1 or later. [/repos/tarball111/src/vstest.e79909063ddfc9d8fd4959e072b2dcf5e8d9d3c1/artifacts/source-build/self/src/src/vstest.console/vstest.console.csproj]

This is required for source build.

This SDK change to the EolTargetFrameworks.targets is what causes the failure.

AB#1396914

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants