Referencing `Microsoft.WindowsAppSDK.WinUI` causes conflicts with transitive dependencies?

[karmeye]

Describe the bug

When changing PacketReference from Microsoft.WindowsAppSDK to Microsoft.WindowsAppSDK.WinUI I get errors like:

Duplicate 'PRIResource' items were included. The .NET SDK includes 'PRIResource' items from your project directory by default. You can either remove these items from your project file, or set the 'EnableDefaultPriItems' property to 'false' if you want to explicitly include them in your project file

Duplicate 'Page' items were included. The .NET SDK includes 'Page' items from your project directory by default. You can either remove these items from your project file, or set the 'EnableDefaultPageItems' property to 'false' if you want to explicitly include them in your project file. For more information, see https://aka.ms/sdkimplicititems. The duplicate items were: 'Controls\DateTimePicker.xaml'; 'Controls\ItemsRepeaterPage.xaml'; ...

@michael-hawker is this because of microsoft/WindowsAppSDK#5811 (comment)?

If so, could we track it here? If it is not related you may close this issue. But according to this comment it seems to be

Looking at that issue, it looks like it is because packages that build on top of WinAppSDK haven't yet moved to just referencing the component packages. So, what happens is if you reference the WinUI component package and also the other library project like CommunityToolKit, its transitive dependency for instance on WinAppSDK 1.6 gets brought down too.

– microsoft/WindowsAppSDK#6015 (comment)

Steps to reproduce

My references

	<ItemGroup>
		<PackageReference Include="CommunityToolkit.Diagnostics" Version="8.4.0" />
		<PackageReference Include="CommunityToolkit.Mvvm" Version="8.4.0" />
		<PackageReference Include="CommunityToolkit.WinUI.Behaviors" Version="8.2.251219" />
		<PackageReference Include="CommunityToolkit.WinUI.Controls.Primitives" Version="8.2.251219" />
		<PackageReference Include="CommunityToolkit.WinUI.Controls.SettingsControls" Version="8.2.251219" />
		<PackageReference Include="CommunityToolkit.WinUI.Controls.Sizers" Version="8.2.251219" />
		<PackageReference Include="CommunityToolkit.WinUI.Controls.TokenizingTextBox" Version="8.2.251219" />
		<PackageReference Include="CommunityToolkit.WinUI.Converters" Version="8.2.251219" />
		<PackageReference Include="CommunityToolkit.WinUI.Extensions" Version="8.2.251219" />
		<PackageReference Include="CommunityToolkit.WinUI.Helpers" Version="8.2.251219" />
		<PackageReference Include="CommunityToolkit.WinUI.UI.Controls.DataGrid" Version="7.1.2" />
		<PackageReference Include="DocumentFormat.OpenXml" Version="3.4.1" />
		<PackageReference Include="Microsoft.Extensions.Hosting" Version="10.0.1" />
		<PackageReference Include="Microsoft.Windows.CsWin32" Version="0.3.264">
			<PrivateAssets>all</PrivateAssets>
		</PackageReference>
		<PackageReference Include="Microsoft.WindowsAppSDK" Version="1.8.251106002" />
		<PackageReference Include="Microsoft.Windows.SDK.BuildTools" Version="10.0.26100.7463" />
		<PackageReference Include="Microsoft.Xaml.Behaviors.WinUI.Managed" Version="3.0.0" />
		<PackageReference Include="Serilog" Version="4.3.0" />
		<PackageReference Include="Serilog.Extensions.Hosting" Version="10.0.0" />
		<PackageReference Include="Serilog.Sinks.Console" Version="6.1.1" />
		<PackageReference Include="Serilog.Sinks.Debug" Version="3.0.0" />
		<PackageReference Include="Serilog.Sinks.File" Version="7.0.0" />
		<PackageReference Include="System.Drawing.Common" Version="10.0.1" />
	</ItemGroup>

Expected behavior

No errors introduced from switching to ...WinUI package

Screenshots

No response

Code Platform

• UWP
• WinAppSDK / WinUI 3
• Web Assembly (WASM)
• Android
• iOS
• MacOS
• Linux / GTK

Windows Build Number

• Windows 10 1809 (Build 17763)
• Windows 10 1903 (Build 18362)
• Windows 10 1909 (Build 18363)
• Windows 10 2004 (Build 19041)
• Windows 10 20H2 (Build 19042)
• Windows 10 21H1 (Build 19043)
• Windows 10 21H2 (Build 19044)
• Windows 10 22H2 (Build 19045)
• Windows 11 21H2 (Build 22000)
• Other (specify)

Other Windows Build number

No response

App minimum and target SDK version

• Windows 10, version 1809 (Build 17763)
• Windows 10, version 1903 (Build 18362)
• Windows 10, version 1909 (Build 18363)
• Windows 10, version 2004 (Build 19041)
• Windows 10, version 2104 (Build 20348)
• Windows 11, version 22H2 (Build 22000)
• Other (specify)

Other SDK version

No response

Visual Studio Version

No response

Visual Studio Build Number

18.1.1

Device form factor

Desktop

Additional context

No response

Help us help you

No, I'm unable to contribute a solution.

[Arlodotexe]

Needs CommunityToolkit/Tooling-Windows-Submodule#292

[karmeye]

Needs CommunityToolkit/Tooling-Windows-Submodule#292

Is it dependent on that issue? or is it that that issue will solve this issue?

[Avid29]

Needs CommunityToolkit/Tooling-Windows-Submodule#292

Is it dependent on that issue? or is it that that issue will solve this issue?

Currently the toolkit targets WinAppSDK 1.6. WinAppSDK 1.6 is not compatible with the most modern version, 1.8. This is the error warning for when you attempt to use them together.

In the meantime, you can revert your project to 1.6, or you can wait for us to update to 1.8 (fingers crossed a version will be released for 1.8 in the next month but who knows for sure).

Hope this helps @karmeye

[karmeye]

Thanks for the clarification @Avid29.

I'll reference the whole Microsoft.WindowsAppSDK as usual for now. I'll track #292 to find out when to try again.