[workload] move SingleProject.targets to Microsoft.Maui.Sdk #3281
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description of Change
Fixes: https://dev.azure.com/devdiv/DevDiv/_workitems/edit/1428787
Currently, if you mimic a design-time build that would happen inside
Visual Studio:
This fails because of the
--no-restore
flag:I was able to reproduce this failure in our template tests in
dotnet.cake
.In 974cac4, several of .NET MAUI's MSBuild targets were moved to
library-packs
, such asMicrosoft.Maui.Controls.Build.Tasks
. Thismeans that files like
Microsoft.Maui.Controls.SingleProject.targets
won't be evaluated until NuGet restore completes.
To solve this problem:
Move
Microsoft.Maui.Controls.SingleProject.targets
andMicrosoft.Maui.Controls.DefaultItems.targets
to theMicrosoft.Maui.Sdk
pack. These.targets
are no longer affected by$(MauiVersion)
, and just exist in the workload.Stop importing these files in
Microsoft.Maui.Controls.targets
inMicrosoft.Maui.Controls.Build.Tasks
.Import these files in
Microsoft.Maui.Sdk.After.targets
.Overall, I think the loss of
$(MauiVersion)
is fine for the moved.targets
files, because they are not invoking MSBuild tasks.The design-time build tests now complete successfully.
PR Checklist
Does this PR touch anything that might affect accessibility?
Nope