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.

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

dotnet add package command should add the id with the same casing as the package #5952

Closed
mishra14 opened this issue Sep 28, 2017 · 1 comment · Fixed by NuGet/NuGet.Client#6304
Closed

dotnet add package command should add the id with the same casing as the package #5952

mishra14 opened this issue Sep 28, 2017 · 1 comment · Fixed by NuGet/NuGet.Client#6304
Labels
Category:Quality Week Issues that should be considered for quality week Functionality:Install The install command in VS/nuget.exe good first issue Issues identified as good for first-time contributors help wanted Considered good issues for community contributions. Priority:2 Issues for the current backlog. Product:dotnet.exe SeQuality Type:Bug
Milestone
Backlog

Comments

@mishra14
Copy link
Contributor

Details about Problem

NuGet product used (NuGet.exe | VS UI | Package Manager Console | dotnet.exe): dotnet.exe

Detailed repro steps so we can see the same problem

  1. dotnet new console

  2. dotnet add package nUgeT.VerSioIng

Expected

A reference to NuGet.Versioning is added.

Actual

A reference to nUgeT.VerSionIng is added. The casing is preserved from the user input.

    <PackageReference Include="nUgeT.VerSionIng" Version="4.3.0" />
@mishra14 mishra14 added Product:VS.Client Type:DCR Design Change Request labels Sep 28, 2017
@mishra14 mishra14 self-assigned this Sep 28, 2017
@mishra14
Copy link
Contributor Author

Related issue in PMC - #5951

@mishra14 mishra14 added this to the 4.5 milestone Sep 28, 2017
@mishra14 mishra14 added Type:Bug and removed Type:DCR Design Change Request labels Oct 2, 2017
@rrelyea rrelyea added Priority:3 Issues under consideration. With enough upvotes, will be reconsidered to be added to the backlog. Priority:2 Issues for the current backlog. and removed Priority:3 Issues under consideration. With enough upvotes, will be reconsidered to be added to the backlog. labels Oct 2, 2017
@rrelyea rrelyea modified the milestones: 4.5, Backlog Oct 2, 2017
@mishra14 mishra14 mentioned this issue Nov 12, 2017
Closed
@mishra14 mishra14 removed their assignment Aug 13, 2018
@ghost ghost added the Status:Inactive Icebox issues not updated for a specific long time label Sep 1, 2022
@nkolev92 nkolev92 added Priority:3 Issues under consideration. With enough upvotes, will be reconsidered to be added to the backlog. and removed Priority:2 Issues for the current backlog. labels Apr 3, 2023
@nkolev92 nkolev92 added help wanted Considered good issues for community contributions. Functionality:Install The install command in VS/nuget.exe Product:dotnet.exe Category:Quality Week Issues that should be considered for quality week good first issue Issues identified as good for first-time contributors and removed Product:VS.Client Status:Inactive Icebox issues not updated for a specific long time Status:Excluded from icebox cleanup labels Mar 6, 2025
@nkolev92 nkolev92 added Priority:2 Issues for the current backlog. and removed Priority:3 Issues under consideration. With enough upvotes, will be reconsidered to be added to the backlog. labels Mar 6, 2025
@nkolev92 nkolev92 mentioned this issue Mar 6, 2025
Merged
3 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Category:Quality Week Issues that should be considered for quality week Functionality:Install The install command in VS/nuget.exe good first issue Issues identified as good for first-time contributors help wanted Considered good issues for community contributions. Priority:2 Issues for the current backlog. Product:dotnet.exe SeQuality Type:Bug
Projects
None yet
Milestone
Backlog
Development

Successfully merging a pull request may close this issue.

Use nuspec casing in dotnet add package NuGet/NuGet.Client
5 participants
@nkolev92 @rrelyea @mishra14 @jeffkl @heng-liu