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

VS2019 VsDevCmd.bat makes dotnet use msbuild v 16 #7304

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 12 additions & 0 deletions release-notes/6.0/known-issues.md
Original file line number Diff line number Diff line change
Expand Up @@ -32,6 +32,18 @@ If you build .NET 6 projects with MSBuild 16.11, for example, you will see the f

`warning NETSDK1182: Targeting .NET 6.0 in Visual Studio 2019 is not supported`

`where dotnet` lists the path(s) to the dotnet cli.

Make sure the \ProgramFiles\ path comes before the \ProgramFiles(x86) path by changing the path envvar.

`where msbuild` lists the path to the msbuild cli.

If no paths are listed `dotnet` will still find a working `msbuild` for .net6.

If `ProgramFiles\Microsoft Visual Studio\**2022**\Enterprise\Common7\Tools\VsDevCmd.bat` have been used to set up a commandline environment for **VS2022**, `where msbuild` and `dotnet` will find the VS2022 msbuild that works.

If `ProgramFiles\Microsoft Visual Studio\**2019**\Enterprise\Common7\Tools\VsDevCmd.bat` have been used to set up a commandline environment for **VS2019**, `where msbuild` and `dotnet` will find the VS2019 msbuild that does not work (v16). Avoid using the VS2019 VsDevCmd.bat fixes the problem.

You can use the .net 6 SDK to target downlevel runtimes in 16.11.

#### 1. dotnet test x64 emulation on arm64 support
Expand Down