Skip to content

Fix NuGet install instructions for v8 component packages#621

Open
GrantMeStrength wants to merge 1 commit intoMicrosoftDocs:mainfrom
GrantMeStrength:jken/fix-nuget-getting-started
Open

Fix NuGet install instructions for v8 component packages#621
GrantMeStrength wants to merge 1 commit intoMicrosoftDocs:mainfrom
GrantMeStrength:jken/fix-nuget-getting-started

Conversation

@GrantMeStrength
Copy link

Problem

The Getting Started page instructs users to search for CommunityToolkit.Uwp and CommunityToolkit.WinUI on NuGet. Since v8.0 (September 2023), these monolithic packages are no longer available:

  • CommunityToolkit.Uwp — returns 404 on NuGet.org
  • CommunityToolkit.WinUI — is an old unlisted v7 package targeting net5.0-windows

Users who follow the current instructions will either find nothing or install an outdated incompatible package.

Fix

  • Update step 2 to use the component package prefix search (CommunityToolkit.Uwp. / CommunityToolkit.WinUI.)
  • Add concrete examples of component package names (e.g. CommunityToolkit.WinUI.Animations)
  • Add a NOTE callout explaining the v8 packaging change so users migrating from older versions understand what changed

Changes

windows/getting-started.md — step 2 updated with correct search prefixes, examples, and a v8 migration note.

The previous instructions directed users to search for the monolithic
packages CommunityToolkit.Uwp and CommunityToolkit.WinUI, which are
no longer available since v8.0 (September 2023). CommunityToolkit.Uwp
returns 404 on NuGet; CommunityToolkit.WinUI is an old unlisted v7 package.

Update step 2 to:
- Use the component prefix search (CommunityToolkit.Uwp. / CommunityToolkit.WinUI.)
- Provide concrete examples of component package names
- Add a NOTE callout explaining the v8 packaging change

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@learn-build-service-prod
Copy link

Learn Build status updates of commit 4348ba6:

✅ Validation status: passed

File Status Preview URL Details
docs/windows/getting-started.md ✅Succeeded View

For more details, please refer to the build report.

@learn-build-service-prod
Copy link

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.

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.

1 participant