[release/6.0] Overbuild caused by PackageReference support (Remove WPF Arcade workaround)

[ryalanms]

Description

[release/6.0] Overbuild caused by PackageReference support (Remove WPF Arcade workaround)

WPF PackageReference support conflicted with an existing Arcade workaround. The WPF workaround (for the Arcade workaround) changed a global property that caused project references to be rebuilt in WPF's temporary project.

This removes the global property.

The issue is described here:
#5448
#4119

Customer Impact

Project references will be built a second time by the internal WPF project.

Regression

This is a regression from 5.0.

Risk

Low.

Testing

Tested the updated WindowsDesktop SDK containing the change against AppCompat applications and WPF samples.

[rainersigwald]

This change looks good.

I'm not sure I understand the order dependencies though. In the end we want three things to happen:

1. This goes into the shipping product.
2. The Arcade SDK workaround is removed.
3. All repos that use the Arcade SDK are updated to use a .NET SDK that has this fix.

Can we do 1 and 2 in parallel? Or will doing 2 break other repos unless they also get 3?

[ryalanms]

Can we do 1 and 2 in parallel? Or will doing 2 break other repos unless they also get 3?

The repos will break if they update to the .NET SDK with the WPF fix, prior to updating to the Arcade SDK with the fix. But I believe both 1 and 2 can be done simultaneously if the version updates are done in the correct order (or together).

[ryalanms]

The PR build won't succeed until WPF takes the Arcade SDK version containing the fix.

[ryalanms]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[ryalanms]

The Arcade SDK update has already flowed to all repos.

[ryalanms]

This was approved by Tactics over email.