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

Fix Microsoft.NETCore.Platforms builds on Unix #57739

Merged
merged 1 commit into from
Aug 19, 2021
Merged

Conversation

ViktorHofer
Copy link
Member

Fixes #57702

The casing of the SDK imported via the Sdk attribute was wrong which lead to:

Microsoft.NETCore.Platforms.csproj : error MSB4236: The SDK 'Microsoft.NET.SDK' specified could not be found.

We should probably backport this into release/6.0-rc1.

The casing of the SDK imported via the Sdk attribute was wrong which lead to:

Microsoft.NETCore.Platforms.csproj : error MSB4236: The SDK 'Microsoft.NET.SDK' specified could not be found.
@ghost
Copy link

ghost commented Aug 19, 2021

Tagging subscribers to this area: @Anipik, @safern, @ViktorHofer
See info in area-owners.md if you want to be subscribed.

Issue Details

Fixes #57702

The casing of the SDK imported via the Sdk attribute was wrong which lead to:

Microsoft.NETCore.Platforms.csproj : error MSB4236: The SDK 'Microsoft.NET.SDK' specified could not be found.

We should probably backport this into release/6.0-rc1.

Author: ViktorHofer
Assignees: ViktorHofer
Labels:

area-Infrastructure-libraries

Milestone: -

@ViktorHofer
Copy link
Member Author

I believe this didn't fail in the Linux allconfigurations build because this only repros when directly restoring the project. If it's restored as part of a dependency in the build graph, it doesn't complain.

@@ -1,4 +1,4 @@
<Project Sdk="Microsoft.NET.SDK">
<Project Sdk="Microsoft.NET.Sdk">
Copy link
Member

@am11 am11 Aug 19, 2021

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think it would had made more sense for SDK resolver to keep names case insensitive (i doubt it would break anything since changing just the casing and publishing a different SDK to nuget.org doesn't work anyway), and especially since there are legit SDKs available with capital casing, e.g. Microsoft.NET.SDK.WorkloadAutoImportPropsLocator, Microsoft.NET.SDK.WorkloadManifestTargetsLocator; it's very easy to make this mistake. 😅

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Agreed...

@ViktorHofer ViktorHofer merged commit f169b71 into main Aug 19, 2021
@ViktorHofer ViktorHofer deleted the ViktorHofer-patch-1 branch August 19, 2021 18:38
@ViktorHofer
Copy link
Member Author

/backport to release/6.0-rc1

@github-actions
Copy link
Contributor

Started backporting to release/6.0-rc1: https://github.com/dotnet/runtime/actions/runs/1148096995

@ghost ghost locked as resolved and limited conversation to collaborators Sep 18, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Unable to update runtime ids using runtimeGroups.props
5 participants