Update Windows SDK projection for testing

[manodasanW]

Description of Change

PR for testing latest Windows SDK projection package

Issues Fixed

Fixes #

[dotnet-policy-service]

Hey there @manodasanW! Thank you so much for your PR! Someone from the team will get assigned to your PR shortly and we'll get it reviewed.

[jsuarezruiz]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 3 pipeline(s).

[jsuarezruiz]

CSC : error CS1705: Assembly 'Microsoft.Maui' with identity 'Microsoft.Maui, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null' uses 'WinRT.Runtime, Version=2.2.0.0, Culture=neutral, PublicKeyToken=99ea127f02d97709' which has a higher version than referenced assembly 'WinRT.Runtime' with identity 'WinRT.Runtime, Version=2.1.0.0, Culture=neutral, PublicKeyToken=99ea127f02d97709' [D:\a\_work\1\s\src\Compatibility\ControlGallery\src\WinUI\Compatibility.ControlGallery.WinUI.csproj]
CSC : error CS1705: Assembly 'Microsoft.Maui.Controls' with identity 'Microsoft.Maui.Controls, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null' uses 'WinRT.Runtime, Version=2.2.0.0, Culture=neutral, PublicKeyToken=99ea127f02d97709' which has a higher version than referenced assembly 'WinRT.Runtime' with identity 'WinRT.Runtime, Version=2.1.0.0, Culture=neutral, PublicKeyToken=99ea127f02d97709' [D:\a\_work\1\s\src\Compatibility\ControlGallery\src\WinUI\Compatibility.ControlGallery.WinUI.csproj]
    9387 Warning(s)
    2 Error(s)

[rmarinho]

@mattleibow you remember anything about getting this working ?

[manodasanW]

I took a look at the binlog and it seems the WindowsSdkPackageVersion set in Directory.Build.Props is not taking effect in all projects as I would expect. It does take effect for some. I see that in the below property group, _MauiTargetPlatformIsWindows is actually false even though Compatibility.ControlGallery.WinUI is targeting the Windows TFM and I do see the correct TFM in the binlog. It seems _MauiTargetPlatformIdentifier is empty which is what is used to set the property.

I wonder if this is some ordering issue for when the TargetFramework gets populated and the Directory.Build.Props running.

  <PropertyGroup Condition="'$(_MauiTargetPlatformIsWindows)' == 'True'">
    <WindowsSdkPackageVersion>10.0.19041.56</WindowsSdkPackageVersion>
  </PropertyGroup>

    <_MauiTargetPlatformIdentifier>$([MSBuild]::GetTargetPlatformIdentifier('$(TargetFramework)'))</_MauiTargetPlatformIdentifier>

[manodasanW]

I took an attempt at trying to address the issue where TargetFramework may not be set yet when Directory.Build.props is run. Not sure if it is going to break anything elsewhere in the cases where it did get set properly but worth seeing what happens in the pipelines.

[jsuarezruiz]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 3 pipeline(s).

[manodasanW]

I believe the current breaks are due to

maui/src/MultiTargeting.targets

Line 26 in 353f1a3

<ItemGroup Condition=" '$(_MauiTargetPlatformIsAndroid)' != 'True' ">

is getting imported before Directory.Build.targets runs as it is explicitly imported by the csproj.

[mattleibow]

Why were all the props moved to the targets file?

[manodasanW]

Why were all the props moved to the targets file?

See this comment. I was basically trying a change to address the issue where TargetFramework wasn't set when Directory.Build.Props got imported for Compatibility.ControlGallery.WinUI causing for those props to be false. It might be we need to continue setting it in the props and then reset it in targets if empty.

[rmarinho]

Why it can t be 10.0.19041.57 ?

[manodasanW]

We can make that them 57 too, it probably was different versions before due to not having the SDK profile changes. But for testing purposes here, 56 or 57 here are fine.