Windows icon indicating copy to clipboard operation
Windows copied to clipboard

Problem with CommunityToolkit.Uwp.Controls.SettingsControls

Open GabrielePepe opened this issue 1 year ago • 2 comments

Describe the bug

Title: Build Fails After Installing CommunityToolkit and Uno.UI Packages

Description:

After installing the following NuGet packages into my project:

  • CommunityToolkit.Uwp.Controls.SettingsControls
  • CommunityToolkit.Winui.Controls.SettingsControls
  • Uno.UI
  • Uno.UI.Toolkit

I encountered build errors preventing the project from compiling successfully. One recurring error message is:

Could not copy the file "obj\x64\Debug\net8.0-windows10.0.19041.0\win-x64\App.xbf" because it was not found.

Steps to Reproduce:

  1. Create a new project.
  2. Install the listed NuGet packages.
  3. Attempt to build the project.

Actual Behavior:

The build fails with the error mentioned above. Additional build errors may appear depending on the project configuration.

Environment:

  • IDE: Visual Studio (version, e.g., 2022 17.x.x)
  • NuGet Package Versions:
    • CommunityToolkit.Uwp.Controls.SettingsControls:
    • CommunityToolkit.Winui.Controls.SettingsControls:
    • Uno.UI:
    • Uno.UI.Toolkit:

Steps to reproduce

The way to reproduce this issue is:
create a project (winui3 packaged)
add CommunityToolkit.WinUi.Controls.SettingsControls
add CommunityToolkit.Uwp.Controls.SettingsControls
add Uno.Ui.Toolkit
add Uno.Ui

Expected behavior

Expected Behavior:

The project should build successfully without errors.

Screenshots

No response

Code Platform

  • [ ] UWP
  • [x] 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)
  • [x] Other (specify)

Other Windows Build number

Windows 11 24h2

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)
  • [x] Windows 11, version 22H2 (Build 22000)
  • [ ] Other (specify)

Other SDK version

No response

Visual Studio Version

2022

Visual Studio Build Number

17.12.1

Device form factor

Desktop

Additional context

No response

Help us help you

Yes, I'd like to be assigned to work on this item.

GabrielePepe avatar Nov 26 '24 14:11 GabrielePepe

Can I ask why you want to add UWP controls to a WASDK/WINUI project?

Jay-o-Way avatar Dec 07 '24 00:12 Jay-o-Way

Can I ask why you want to add UWP controls to a WASDK/WINUI project?

You need to add both dependencies together before you can use it.

Endier avatar Jan 09 '25 02:01 Endier

Can I ask why you want to add UWP controls to a WASDK/WINUI project?

You need to add both dependencies together before you can use it.

You should never have both UWP and WinUI packages installed alongside each other, as they'll interfere with each other.

  • If you're in a UWP project (with or without uno), installed the *.Uwp.* package.
  • If you're in a WindowsAppSDK or WinUI 3 project, install the *.WinUI.* package.

Arlodotexe avatar Aug 07 '25 16:08 Arlodotexe