Skip to content

Migration (.NET 11): document compatibility package removal - #3404

Merged
davidortinau merged 2 commits into
mainfrom
jfversluis-compatibility-package-docs
Jul 15, 2026
Merged

Migration (.NET 11): document compatibility package removal#3404
davidortinau merged 2 commits into
mainfrom
jfversluis-compatibility-package-docs

Conversation

@jfversluis

@jfversluis jfversluis commented Jul 8, 2026

Copy link
Copy Markdown
Member

Summary

  • Documents that the optional Microsoft.Maui.Controls.Compatibility NuGet package is no longer built or shipped for .NET 11 and later.
  • Monikers the multi-project migration package-reference guidance so .NET 10 and earlier preserve the compatibility package reference, while .NET 11+ only references Microsoft.Maui.Controls.
  • Adds a .NET 11+ custom renderer note that advises migrating away from APIs/renderers that were only available from the opt-in compatibility package, without removing valid shimmed renderer guidance still included with Microsoft.Maui.Controls.

Source verification

  • Upstream MAUI PR: Remove MAUI compatibility package maui#35870
  • Verified release/11.0.1xx-preview6 no longer contains src/Compatibility/Core/src/Compatibility.csproj.
  • Verified selected shimmed renderer base types and RelativeLayout still exist under src/Controls/src/Core in release/11.0.1xx-preview6.

Validation

  • Ran markdownlint-cli2 on the changed docs.
  • Checked whitespace and moniker block balance.

Internal previews

📄 File 🔗 Preview link
docs/migration/custom-renderers.md docs/migration/custom-renderers
docs/migration/multi-project-to-multi-project.md docs/migration/multi-project-to-multi-project

Document that Microsoft.Maui.Controls.Compatibility is no longer built or shipped in .NET 11 and later, while preserving the older package-reference guidance behind monikers.

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Copilot AI review requested due to automatic review settings July 8, 2026 15:32
@jfversluis
jfversluis requested a review from a team as a code owner July 8, 2026 15:32
@learn-build-service-prod

Copy link
Copy Markdown
Contributor

PoliCheck Scan Report

The following report lists PoliCheck issues in PR files. Before you merge the PR, you must fix all severity-1 and severity-2 issues. The AI Review Details column lists suggestions for either removing or replacing the terms. If you find a false positive result, mention it in a PR comment and include this text: #policheck-false-positive. This feedback helps reduce false positives in future scans.

✅ No issues found

More information about PoliCheck

Information: PoliCheck | Severity Guidance | Term
For any questions: Try searching the learn.microsoft.com contributor guides or post your question in the Learn support channel.

@learn-build-service-prod

Copy link
Copy Markdown
Contributor

Learn Build status updates of commit 8fbd0a9:

✅ Validation status: passed

File Status Preview URL Details
docs/migration/custom-renderers.md ✅Succeeded View (>=net-maui-8.0)
docs/migration/multi-project-to-multi-project.md ✅Succeeded View (>=net-maui-8.0)

For more details, please refer to the build report.

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Documents the removal of the optional Microsoft.Maui.Controls.Compatibility NuGet package for .NET MAUI on .NET 11+ and updates migration guidance so readers on earlier versions keep the compatibility reference while .NET 11+ guidance references only Microsoft.Maui.Controls.

Changes:

  • Monikered the “Add package references” section to keep Microsoft.Maui.Controls.Compatibility guidance for <=net-maui-10.0 and remove it for >=net-maui-11.0.
  • Added .NET 11+ guidance to remove the compatibility package reference and migrate off APIs/renderers that only existed in the opt-in compatibility package.
  • Added a .NET 11+ IMPORTANT note to the custom renderers migration doc clarifying the compatibility package removal while keeping shimmed renderer guidance.
Show a summary per file
File Description
docs/migration/multi-project-to-multi-project.md Adds monikered package-reference guidance for .NET 11+ compatibility package removal.
docs/migration/custom-renderers.md Adds a .NET 11+ IMPORTANT note about the compatibility package removal and migration implications.

Copilot's findings

  • Files reviewed: 2/2 changed files
  • Comments generated: 2

Comment thread docs/migration/multi-project-to-multi-project.md Outdated
Comment thread docs/migration/multi-project-to-multi-project.md Outdated
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
@learn-build-service-prod

Copy link
Copy Markdown
Contributor

PoliCheck Scan Report

The following report lists PoliCheck issues in PR files. Before you merge the PR, you must fix all severity-1 and severity-2 issues. The AI Review Details column lists suggestions for either removing or replacing the terms. If you find a false positive result, mention it in a PR comment and include this text: #policheck-false-positive. This feedback helps reduce false positives in future scans.

✅ No issues found

More information about PoliCheck

Information: PoliCheck | Severity Guidance | Term
For any questions: Try searching the learn.microsoft.com contributor guides or post your question in the Learn support channel.

@learn-build-service-prod

Copy link
Copy Markdown
Contributor

Learn Build status updates of commit f511920:

✅ Validation status: passed

File Status Preview URL Details
docs/migration/custom-renderers.md ✅Succeeded View (>=net-maui-8.0)
docs/migration/multi-project-to-multi-project.md ✅Succeeded View (>=net-maui-8.0)

For more details, please refer to the build report.

@davidortinau
davidortinau merged commit df57021 into main Jul 15, 2026
7 checks passed
@davidortinau
davidortinau deleted the jfversluis-compatibility-package-docs branch July 15, 2026 18:48
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

Successfully merging this pull request may close these issues.

3 participants