-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Overbuild caused by PackageReference support #5448
Comments
This was missed as part of 6.0. Both the Arcade workaround and WPF's global property should be removed. |
@ryalanms Do you think we can get both in for GA? I'd really like to avoid shipping this way. |
@mmitche: This will require an Arcade change. We will need to disable (or remove) the Arcade WPF temp project workaround at the same time WPF's global The property is Or the whole change: edit: We can disable |
Yes, it can make GA. Can you make a tell mode for the arcade change, and then an ask mode for the WPF change? |
Here is the Arcade change: |
The
_wpftmp
build inside a normal project is built with a global property set:$(_WpfTempProjectNuGetFilePathNoExt)
. It also now runsResolveProjectReferences
by default. This combines to cause overbuild of the referenced projects, because MSBuild treats projects as distinct when they have different global properties.This can be observed in build output:
Note the doubled
Library -> S:\play\wpf_incremental\Library\bin\Debug\net5.0\Library.dll
: that project is building twice.The global property for the
_wpftmp
project is set here:wpf/src/Microsoft.DotNet.Wpf/src/PresentationBuildTasks/Microsoft/Build/Tasks/Windows/GenerateTemporaryTargetAssembly.cs
Lines 284 to 286 in fb1a859
Timeline:
$(_WpfTempProjectNuGetFilePathNoExt)
to .NET's Arcade SDK.$(IncludePackageReferencesDuringMarkupCompilation)
(defaulted tofalse
). This introduced this race condition._WpfTempProjectNuGetFilePathNoExt
to empty.$(IncludePackageReferencesDuringMarkupCompilation)
on by default in the SDK.The text was updated successfully, but these errors were encountered: