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

Workaround to allow rc1 uptake #15076

Merged
merged 1 commit into from
Sep 11, 2024
Merged

Conversation

rainersigwald
Copy link
Member

This works around dotnet/sdk#43339 for Arcade projects, unblocking
updating to .NET SDK 9.0.100-rc.1, even when official or PR builds use
Visual Studio 17.11.

Vetted in dotnet/msbuild#10643.

This works around dotnet/sdk#43339 for Arcade projects, unblocking
updating to .NET SDK 9.0.100-rc.1, even when official or PR builds use
Visual Studio 17.11.
@@ -184,4 +184,29 @@
</ItemGroup>
</Target>

<!-- BEGIN workaround for https://github.com/dotnet/sdk/issues/43339; remove after updated to VS 17.12 or a future 17.11 patch -->
<Target Name="WorkaroundDotnetSdk43339" BeforeTargets="ResolvePackageAssets" Condition=" '$(MSBuildRuntimeType)' == 'Full' and $([MSBuild]::VersionLessThan($(MSBuildVersion), 17.12.0))">
Copy link
Member

Choose a reason for hiding this comment

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

Any other targets that might load NuGet and hit this?

Copy link
Member Author

Choose a reason for hiding this comment

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

Probably but I don't know of any today. I guess it'd be maximally conservative to do this as an InitialTargets or something, but that feels pretty bad . . .

Copy link
Member

Choose a reason for hiding this comment

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

since arcade flows directly into the repos any cases should be visible in the flow pr and easy fix without making anything worse

Copy link
Member

Choose a reason for hiding this comment

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

I guess another repo could always add a new target like this:

<Target Name="MyRepoWorkaroundDotnetSdk43339" DependsOnTargets="WorkaroundDotnetSdk43339" BeforeTargets="MyBrokenTarget" />

Copy link
Member Author

Choose a reason for hiding this comment

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

Yeah, the reason to push this in Arcade is to avoid having to work around everywhere but it's possible to do so.

@lewing lewing mentioned this pull request Sep 11, 2024
1 task
@lewing lewing merged commit a1d1655 into dotnet:main Sep 11, 2024
11 checks passed
@lewing
Copy link
Member

lewing commented Sep 11, 2024

/backport to release/9.0

Copy link
Contributor

Started backporting to release/9.0: https://github.com/dotnet/arcade/actions/runs/10817834607

@rainersigwald rainersigwald deleted the work-around-sdk-43339 branch September 11, 2024 19:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants