Switch from wux to mux where possible #157
Conversation
|
@stevenbrix - this requires a fix to the WinUI nuget for native clients: @manodasanW - need confirmation on what's in "WUX" (but outside that namespace) and thus needs to be mapped to MUX - e.g., Windows.UI.Color |
| @@ -21,6 +21,14 @@ | |||
| </Target> | |||
|
|
|||
| <Target Name="GenerateProjection" BeforeTargets="DispatchToInnerBuilds;Build" Condition="'$(GenerateTestProjection)' == 'true'"> | |||
| <PropertyGroup> | |||
| <!--PkgMicrosoft_WinUI is set in in obj\*.csproj.nuget.g.props with TargetFramework condition, doesn't support multi-targeting--> | |||
| <PkgMicrosoft_WinUI Condition="'$(PkgMicrosoft_WinUI)'==''">$(NuGetPackageFolders)microsoft.winui\$(MicrosoftWinUIVersion)</PkgMicrosoft_WinUI> | |||
There was a problem hiding this comment.
@stevenbrix - not sure whether this is a bug in WinUI or not
…inUI nuget issues
Scottj1s
changed the title
|
WinUIProjection.cs has a few workarounds for WinUI nuget issues. These can be removed when the WinUI nuget is free of Windows.UI.Xaml and Windows.UI.Text references. To work around the native targets file issue (importing missing Microsoft.UI.targets and Microsoft.UI.Composition.targets), I just updated to a newer version of the Nuget. |
I'm not expecting this particular issue to go way until after Preview1, is that ok?
can you update to version |
|
As part of moving to that Nuget, you should also be able to remove |
Instead of 3.0.0-preview1.200420.0-CI (which is what I've done)? |
Are you asking to move to 3.0.0-preview1.200419.0-CI across the board (managed and native projects)? OK, that seems to satisfy all projects - done |
fixes #147