Skip to content

Update the dotnet CLI docs to document the new noun-first command forms #45001

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

Closed
baronfel opened this issue Feb 24, 2025 · 1 comment
Closed

Comments

@baronfel
Copy link
Member

baronfel commented Feb 24, 2025

Type of issue

Missing information

Description

In 9.0.300 and onwards the dotnet CLI added several new noun-first command (dotnet package add) for existing verb-first forms (dotnet add package). This was done based on significant user feedback about mixing up commands, since the majority of the subcommand-based commands in the SDK were noun-first.

In addition, many other CLIs that users interact with as part of their work have conditioned them to expect noun-first grammars.

Specifically, the following new forms are available:

  • dotnet package list
  • dotnet reference list
  • dotnet package add
  • dotnet reference add
  • dotnet package remove
  • dotnet reference remove

The existing, verb-first forms of these commands have not been removed - they remain functional and will not be removed in the near future. We may add a notification message to their use informing users about the new noun-first forms like we've done for the older dotnet new subcommands (picture below).

Image

Implementation PR: dotnet/sdk#45384
Tracking Issue: dotnet/sdk#9650

Page URL

https://learn.microsoft.com/en-us/dotnet/core/tools/

Content source URL

https://github.com/dotnet/docs/blob/main/docs/core/tools/index.md

Document Version Independent Id

c6859ca6-e2b1-3645-872c-60390ffd429a

Article author

@tdykstra

Metadata

  • ID: b7e47565-cc59-b1a6-24be-0143c550c0b2
  • PlatformId: 71f88ad0-c497-bd84-bcae-a271c6be9107
  • Service: dotnet-fundamentals

Related Issues

@dotnet-policy-service dotnet-policy-service bot added the ⌚ Not Triaged Not triaged label Feb 24, 2025
@gewarren gewarren self-assigned this Feb 28, 2025
@dotnetrepoman dotnetrepoman bot added the 🗺️ mapQUEST Only used as a way to mark an issue as updated for quest. RepoMan should instantly remove it. label Mar 4, 2025
@dotnet-policy-service dotnet-policy-service bot removed the 🗺️ mapQUEST Only used as a way to mark an issue as updated for quest. RepoMan should instantly remove it. label Mar 4, 2025
@gewarren
Copy link
Contributor

gewarren commented Apr 3, 2025

This was fixed by #43917.

@gewarren gewarren closed this as completed Apr 3, 2025
@github-project-automation github-project-automation bot moved this from 🔖 Ready to ✅ Done in dotnet/docs April 2025 sprint project Apr 3, 2025
@gewarren gewarren added the 🗺️ mapQUEST Only used as a way to mark an issue as updated for quest. RepoMan should instantly remove it. label Apr 3, 2025
@dotnet-policy-service dotnet-policy-service bot removed the 🗺️ mapQUEST Only used as a way to mark an issue as updated for quest. RepoMan should instantly remove it. label Apr 3, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Development

No branches or pull requests

2 participants