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

Update the .NET Uninstall Tool page to proper CLI reference and conceptual guide #40883

Closed
adegeo opened this issue May 14, 2024 · 0 comments · Fixed by #42033
Closed

Update the .NET Uninstall Tool page to proper CLI reference and conceptual guide #40883

adegeo opened this issue May 14, 2024 · 0 comments · Fixed by #42033
Assignees
Labels
doc-enhancement Improve the current content [org][type][category] dotnet-fundamentals/svc in-pr This issue will be closed (fixed) by an active pull request. Pri1 High priority, do before Pri2 and Pri3 📌 seQUESTered Identifies that an issue has been imported into Quest. resolved-by-customer Indicates issues where the customer no longer needs any help. [org][resolution]

Comments

@adegeo
Copy link
Contributor

adegeo commented May 14, 2024

Type of issue

Outdated article

Description

Currently, this page doesn't really follow our format for content. The page is a mix of conceptual and CLI reference. This should be converted to two articles:

  1. The CLI reference for the tool. (for example https://learn.microsoft.com/dotnet/core/tools/dotnet-build)
  2. The how-to type of information that describes install/uninstall/common tasks.

How to info could go into Remove the .NET runtime and SDK.

Inspired by #36040

Page URL

https://learn.microsoft.com/en-us/dotnet/core/additional-tools/uninstall-tool?tabs=windows

Content source URL

https://github.com/dotnet/docs/blob/main/docs/core/additional-tools/uninstall-tool.md

Document Version Independent Id

3145ef37-2a19-e3ca-ba78-95c2f1a41a6b

Article author

@sfoslund

Metadata

  • ID: 289d3b2b-8b21-d0a0-10fa-9a8b3fdb62ce
  • Service: dotnet-fundamentals

Associated WorkItem - 255192

@adegeo adegeo self-assigned this May 14, 2024
@dotnet-bot dotnet-bot added the ⌚ Not Triaged Not triaged label May 14, 2024
@issues-automation issues-automation bot added dotnet-fundamentals/svc Pri1 High priority, do before Pri2 and Pri3 labels May 14, 2024
@adegeo adegeo added the doc-enhancement Improve the current content [org][type][category] label May 14, 2024
@dotnet-bot dotnet-bot removed the ⌚ Not Triaged Not triaged label May 14, 2024
@adegeo adegeo added the 🗺️ reQUEST Triggers an issue to be imported into Quest. label May 14, 2024
@sequestor sequestor bot added 📌 seQUESTered Identifies that an issue has been imported into Quest. and removed 🗺️ reQUEST Triggers an issue to be imported into Quest. labels May 15, 2024
@BillWagner BillWagner added the 🗺️ mapQUEST Only used as a way to mark an issue as updated for quest. RepoMan should instantly remove it. label Jul 15, 2024
@dotnet-policy-service dotnet-policy-service bot added the in-pr This issue will be closed (fixed) by an active pull request. label Aug 5, 2024
@dotnet-bot dotnet-bot removed the 🗺️ mapQUEST Only used as a way to mark an issue as updated for quest. RepoMan should instantly remove it. label Aug 5, 2024
@dotnet-bot dotnet-bot added the resolved-by-customer Indicates issues where the customer no longer needs any help. [org][resolution] label Aug 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
doc-enhancement Improve the current content [org][type][category] dotnet-fundamentals/svc in-pr This issue will be closed (fixed) by an active pull request. Pri1 High priority, do before Pri2 and Pri3 📌 seQUESTered Identifies that an issue has been imported into Quest. resolved-by-customer Indicates issues where the customer no longer needs any help. [org][resolution]
Projects
No open projects
Status: 👀 In review
Status: Slipped
Development

Successfully merging a pull request may close this issue.

3 participants