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

Do not force .NET SDK 8.0.400 to increase minimum version number #13775

Open
zivkan opened this issue Sep 7, 2024 · 0 comments
Open

Do not force .NET SDK 8.0.400 to increase minimum version number #13775

zivkan opened this issue Sep 7, 2024 · 0 comments
Assignees
Labels
Priority:1 High priority issues that must be resolved in the current sprint. Product:dotnet.exe RegressionFromPreviousRTM A regression from the last RTM. Example: worked in 6.2, doesn't work in 6.3 Type:Bug
Milestone

Comments

@zivkan
Copy link
Member

zivkan commented Sep 7, 2024

NuGet Product Used

dotnet.exe

Product Version

8.0.400

Worked before?

8.0.300

Impact

None

Repro Steps & Context

https://learn.microsoft.com/en-us/dotnet/core/porting/versioning-sdk-msbuild-vs#targeting-and-support-rules

.NET documents 8.0.400 as having a minimum VS version of 17.8. However, because NuGet compiles against a higher version of MSBuild, it doesn't work. (note, there's a pull request to update the docs, which might change it given NuGet broke earlier VS)

NuGet that ships in the 8.0.400 SDK needs to respect the .NET SDK's minimum VS version number.

Verbose Logs

No response

@zivkan zivkan added Priority:1 High priority issues that must be resolved in the current sprint. Type:Bug RegressionFromPreviousRTM A regression from the last RTM. Example: worked in 6.2, doesn't work in 6.3 Product:dotnet.exe labels Sep 7, 2024
@zivkan zivkan self-assigned this Sep 7, 2024
@zivkan zivkan changed the title Do not force Do not force .NET SDK 8.0.400 to increase minimum version number Sep 7, 2024
@zivkan zivkan added this to the 6.11 milestone Sep 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Priority:1 High priority issues that must be resolved in the current sprint. Product:dotnet.exe RegressionFromPreviousRTM A regression from the last RTM. Example: worked in 6.2, doesn't work in 6.3 Type:Bug
Projects
None yet
Development

No branches or pull requests

1 participant