Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

UWP .NET9 => v8.2.241221-build.1360 wrong dependencies (Uno.UI) #590

Open
3 of 24 tasks
jp-weber opened this issue Dec 21, 2024 · 1 comment
Open
3 of 24 tasks

UWP .NET9 => v8.2.241221-build.1360 wrong dependencies (Uno.UI) #590

jp-weber opened this issue Dec 21, 2024 · 1 comment

Comments

@jp-weber
Copy link

Describe the bug

With the latest nuget build v8.2.241221-build.1360 the dependencies seem to be pulled incorrectly, which means that Uno packages are included in a UWP project

Steps to reproduce

1. Create a new UWP project with dotnet 9
2. Install for example the package 'CommunityToolkit.Uwp.Controls.SettingsControls'
3. Build the app

Expected behavior

No Uno packages.

Screenshots

Image

Image

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

2022

Visual Studio Build Number

No response

Device form factor

No response

Additional context

No response

Help us help you

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

@Sergio0694
Copy link
Member

Same as CommunityToolkit/Tooling-Windows-Submodule#238. When we merge #591 that should provide a workaround until we further split the packages. You should be able to try the new packages as soon as this is merged.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants