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

Always use the MSIX tooling #6068

Merged
merged 2 commits into from
Apr 13, 2022
Merged

Always use the MSIX tooling #6068

merged 2 commits into from
Apr 13, 2022

Conversation

mattleibow
Copy link
Member

@mattleibow mattleibow commented Apr 13, 2022

Description of Change

Make sure to use the new tooling everywhere.

If we try using the default tooling for class libraries, it tries to load net framework tasks in a dotnet build scenario.

Issues Fixed

Fixes #5886

@mattleibow mattleibow added the area-single-project Splash Screen, Multi-Targeting, MauiFont, MauiImage, MauiAsset, Resizetizer label Apr 13, 2022
@mattleibow mattleibow added this to the 6.0.300-rc.2 milestone Apr 13, 2022
@mattleibow mattleibow self-assigned this Apr 13, 2022
@mattleibow mattleibow added p/0 Work that we can't release without fatal labels Apr 13, 2022
@rmarinho rmarinho merged commit a5cf6e0 into main Apr 13, 2022
@rmarinho rmarinho deleted the dev/msix branch April 13, 2022 16:04
@github-actions github-actions bot locked and limited conversation to collaborators Dec 21, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area-single-project Splash Screen, Multi-Targeting, MauiFont, MauiImage, MauiAsset, Resizetizer p/0 Work that we can't release without
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Unable to build Windows class libraries with dotnet build
2 participants