Microsoft-UI-Xaml V2.8 conflict with Microsoft.Toolkit.Uwp.UI.Controls V7.1.2

[OneFingerCodingWarrior]

Describe the bug

1、After Update to V2.8, got the following error
PRI175: 0x80073b0f - Processing Resources failed with error: Duplicate Entry.
2、V2.7.1 works fine

Steps to reproduce the bug

Please compile the attachment project

Expected behavior

No response

Screenshots

No response

NuGet package version

Microsoft.UI.Xaml 2.8.0

Windows app type

• UWP
• Win32

Device form factor

Desktop

Windows version

Windows 10 (20H2): Build 19042

Additional context

App3.zip

[MagicAndre1981]

this often happens with version mismatch of dependencies. Toolkit is using 2.7, so the version needs to be increase in toolkit. Raise an issue there

[OneFingerCodingWarrior]

The problem is if Microsoft.Toolkit.Uwp.UI.Controls is referenced in the main project , everything is fine.
And error arise only when it is referenced in a class library .
Maybe i should wait Toolkit update dependencies to WinUI 2.8, and then try again.

[OneFingerCodingWarrior]

One more question: if Toolkit is targeting 2.7, why 2.71 is fine, but 2.8.0 is not ?

[NGame1]

The problem is if Microsoft.Toolkit.Uwp.UI.Controls is referenced in the main project , everything is fine. And error arise only when it is referenced in a class library . Maybe i should wait Toolkit update dependencies to WinUI 2.8, and then try again.

I also have the same issue. It's also fine on 2.7.2 just 2.8 having the issue.
I also have the following error too on 2.8, however, 2.7.x versions are fine.
PRI277: 0x80073b0f - Conflicting values for resource 'Files/Microsoft.UI.Xaml/DensityStyles/Compact.xbf'

[krschau]

I suspect that @MagicAndre1981 is right, and the issue is that WCT is still pointing to 2.7.1. @michael-hawker, do you agree?

[MagicAndre1981]

One more question: if Toolkit is targeting 2.7, why 2.71 is fine, but 2.8.0 is not ?

I have no idea, I just remember that this error occurred in the past if version mismatches occurred for Xamarin.Forms or Microsoft.NETCore.UniversalWindowsPlatform

[NGame1]

Microsoft.NETCore.UniversalWindowsPlatform

I'm using Microsoft.NETCore.UniversalWindowsPlatform 6.2.14 on main project and class libraries.

[Arlodotexe]

👋 After some investigation, I found that this issue is still present when the Community Toolkit is removed from the equation.

It can be reproduced using only class libraries and the Microsoft.UI.Xaml nuget package:

After additional testing, the issue will go away if either of these conditions are met:

• The Microsoft.UI.Xaml version used in the transitive dependency matches the version used in the referencing project.
• Or, explicitly install the Microsoft.UI.Xaml package version you'd like to you in the project that references the problematic package/project with a reference to a lower version (install to ClassLibraryWithWinUI28 in the screnshot above)

Since this issue can be reproduced without the Toolkit, we're recommending a workaround for developers and handing this back to the WinUI team from here.

[github-actions]

This issue is stale because it has been open 180 days with no activity. Remove stale label or comment or this will be closed in 5 days.

[antokhio]

Just bumped in to this, as soon as i reference
Microsoft.Toolkit.Uwp.UI.Controls Main project and Class Library i get PRI175: 0x80073b0f - Processing Resources failed with error: Duplicate Entry.

omg 4 hours to waste because of this

EDIT:
seems happens if Microsoft.Toolkit.Uwp.UI.Controls installed without Microsoft.UI.Xaml in Class Library project

[michaelrinderle]

Just bumped in to this, as soon as i reference Microsoft.Toolkit.Uwp.UI.Controls Main project and Class Library i get PRI175: 0x80073b0f - Processing Resources failed with error: Duplicate Entry.

omg 4 hours to waste because of this

EDIT: seems happens if Microsoft.Toolkit.Uwp.UI.Controls installed without Microsoft.UI.Xaml in Class Library project

I can confirm you need Microsoft.UI.Xaml in a UWP class library if you use Microsoft.Toolkit.Uwp.UI.Controls.

Thank for the pointer! I would have spent even more time than that if I didn't find your post!