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

Keep apphostpack version in sync with targeting and runtime pack version #10030

Merged
merged 9 commits into from
Nov 5, 2024

Conversation

ViktorHofer
Copy link
Member

@ViktorHofer ViktorHofer commented Nov 4, 2024

Unblocks dotnet/sdk#43015
Alternative to #10028

WPF uses vcxprojs which don't support downloading PackageReferences via NuGet. There's an experimental feature switch but enabling that didn't work (see #10028). Therefore, vcxprojs are dependent on the pre-downloaded "packs" folder content in the SDK layout.
Today, wpf projects target net9.0 with a 9.0 SDK but when building the repo inside the VMR, a 10.0.100-alpha SDK is used. That SDK only contains 10.0.0-alpha targeting packs, runtime packs and apphosts. But as wpf targets net9.0 it needs the 9.0.0 assets. The solution to that is using the "live" runtime assets to not depend on the SDK.
This repo already uses live assets from runtime but that logic is disabled for vcxprojs and didn't include apphost packs. This PR enables that.

The Tools.props change and the added target in RuntimeFrameworkReference.targets can be deleted when vcxprojs support NuGet restore. I don't want to block the SDK PR on such a change though as that might take longer.

Fixes #

Main PR

Description

Customer Impact

Regression

Testing

Risk

Microsoft Reviewers: Open in CodeFlow

Unblocks dotnet/sdk#43015

WPF uses a "live" version of the .NETCoreApp targeting and runtime pack. Also use the live version for the apphost pack so that vcxprojs don't depend on the version inside the SDK.
@ViktorHofer ViktorHofer requested review from a team as code owners November 4, 2024 10:06
@dotnet-policy-service dotnet-policy-service bot added the PR metadata: Label to tag PRs, to facilitate with triage label Nov 4, 2024
@ViktorHofer ViktorHofer closed this Nov 4, 2024
@ViktorHofer ViktorHofer deleted the ViktorHofer-patch-1 branch November 4, 2024 10:13
@ViktorHofer ViktorHofer restored the ViktorHofer-patch-1 branch November 4, 2024 16:42
@ViktorHofer ViktorHofer deleted the ViktorHofer-patch-1 branch November 4, 2024 16:42
@ViktorHofer ViktorHofer restored the ViktorHofer-patch-1 branch November 4, 2024 16:42
@ViktorHofer ViktorHofer reopened this Nov 4, 2024
akoeplinger
akoeplinger previously approved these changes Nov 4, 2024
eng/Tools.props Outdated Show resolved Hide resolved
@ViktorHofer
Copy link
Member Author

ViktorHofer commented Nov 4, 2024

@dotnet/wpf-developers can you please review/approve this PR? This is needed to unblock the VMR and .NET 10 / net10.0 effort in the SDK. We can eventually get some of these changes cleaned-up / removed by enabling vcxproj NuGet support.

@dipeshmsft dipeshmsft merged commit 4ac3507 into main Nov 5, 2024
8 checks passed
@dipeshmsft dipeshmsft deleted the ViktorHofer-patch-1 branch November 5, 2024 17:45
@github-actions github-actions bot locked and limited conversation to collaborators Dec 6, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
PR metadata: Label to tag PRs, to facilitate with triage
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants