Thanks to visit codestin.com
Credit goes to github.com

Skip to content

feat!: Drop UWP support and migrate to Uno.Sdk #1500

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.

Sign up for GitHub

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

Jump to bottom
Draft
Copilot wants to merge 4 commits into
base: main
Choose a base branch
from
Draft

feat!: Drop UWP support and migrate to Uno.Sdk #1500

Copilot wants to merge 4 commits into from

Conversation

Copy link

Copilot AI commented Nov 16, 2025 •
edited
Loading

GitHub Issue (If applicable): #1541

PR Type

  • Feature
  • Build or CI related changes
  • Documentation content changes

What is the current behavior?

WinUI library projects use MSBuild.Sdk.Extras/3.0.38 and maintain separate UWP lineage projects (Uno.Toolkit.UI, Uno.Toolkit.UI.Material, Uno.Toolkit.UI.Cupertino) targeting uap10.0.19041, blocking access to modern C# language features.

What is the new behavior?

All WinUI library projects migrated to Uno.Sdk.Private with single-project structure. UWP projects and packages discontinued.

Migration Changes

Removed UWP Projects:

  • Uno.Toolkit.UI.csproj
  • Uno.Toolkit.UI.Material.csproj
  • Uno.Toolkit.UI.Cupertino.csproj

Migrated to Uno.Sdk.Private:

  • All 6 WinUI library projects (core, Material, Cupertino, Skia, Markup variants)
  • Removed MSBuild.Sdk.Extras from global.json
  • Platform detection conditions updated for Uno.Sdk compatibility (e.g., '$(IsAndroid)' == 'true')
  • Implicit package references now handled by SDK (Uno.WinUI, WindowsAppSDK, etc.)

Solution Files Updated:

  • Removed UWP projects from Uno.Toolkit.sln
  • Removed UWP projects from Uno.Toolkit-packages.slnf solution filter

Target Framework Updates:

  • Windows TFM: net9.0-windows10.0.19041 → net9.0-windows10.0.26100
  • No longer multi-targeting UWP

Documentation:

  • Updated getting-started.md with UWP discontinuation notice
  • Removed UWP from package descriptions

Breaking Changes

Discontinued Packages (use 6.x for UWP):

  • Uno.Toolkit.UI
  • Uno.Toolkit.UI.Material
  • Uno.Toolkit.UI.Cupertino

Migration Path:
Replace with WinUI equivalents (namespace remains Uno.Toolkit.UI):

  • Uno.Toolkit.UI → Uno.Toolkit.WinUI
  • Uno.Toolkit.UI.Material → Uno.Toolkit.WinUI.Material
  • Uno.Toolkit.UI.Cupertino → Uno.Toolkit.WinUI.Cupertino

PR Checklist

  • Tested code with current supported SDKs
  • Tested the changes where applicable:
    • UWP (discontinued)
    • WinUI
    • iOS
    • Android
    • WASM
    • MacOS
  • Updated the documentation as needed:
  • Runtime Tests and/or UI Tests for the changes have been added (for bug fixes / features) (if applicable)
  • Contains NO breaking changes
  • Associated with an issue (GitHub or internal)
  • Commits must be following the Conventional Commits specification.

Other information

Aligns with Uno.Extensions migration (#2437). Unblocks C# language features (nullable attributes, System.Index/Range) previously restricted by UWP.

Internal Issue (If applicable): N/A

Original prompt

This section details on the original issue you should resolve

<issue_title>Drop UWP + use Uno.Sdk</issue_title>
<issue_description>Following in the steps of Extensions (#2437), we should be dropping UWP support and the UWP samples as well as moving the projects and samples to use Uno.Sdk/single project</issue_description>

<agent_instructions>Convert the WinUI library projects to Uno.Sdk projects. We should also be updating the WinUI based sample app to use Uno.Sdk</agent_instructions>

Comments on the Issue (you are @copilot in this section)

@Xiaoy312 just to be clear, are we discontinuing the `uwp` line of packages? @kazo0 > just to be clear, are we discontinuing the `uwp` line of packages?

Yes</comment_new>
<comment_new>@Xiaoy312
bump
UWP is also blocking us from using any of the new language features(like nullable attributes, system.index and range) and other new stuffs...</comment_new>

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.

@CLAassistant
Copy link

CLAassistant commented Nov 16, 2025

CLA assistant check
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
You have signed the CLA already but the status is still pending? Let us recheck it.

Copilot AI changed the title [WIP] Drop UWP support and migrate to Uno.Sdk feat!: Drop UWP support and migrate to Uno.Sdk Nov 16, 2025
Copilot AI requested a review from kazo0 November 16, 2025 02:07
@kazo0
Copy link
Contributor

kazo0 commented Nov 16, 2025

@copilot update the .slnf file to remove the deleted non-WinUI projects

Copy link
Author

Copilot AI commented Nov 16, 2025

@copilot update the .slnf file to remove the deleted non-WinUI projects

Updated the .slnf file to remove the three deleted UWP projects (Uno.Toolkit.UI.csproj, Uno.Toolkit.UI.Material.csproj, and Uno.Toolkit.UI.Cupertino.csproj) in commit 1956208.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@kazo0 kazo0 Awaiting requested review from kazo0

At least 1 approving review is required to merge this pull request.

Assignees

@kazo0 kazo0

Copilot code review Copilot

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

Drop UWP + use Uno.Sdk

3 participants

@CLAassistant @kazo0