Skip to content

Navigation Menu

Explore
By company size
By use case
By industry
View all solutions
Topics
- AI
- DevOps
- Security
- Software Development
- View all
Explore
- GitHub Sponsors
  Fund open source developers
- The ReadME Project
  GitHub community articles
Repositories
- Enterprise platform
  AI-powered developer platform
Available add-ons
Pricing

Search code, repositories, users, issues, pull requests...

Search

Clear

Search syntax tips

Provide feedback

We read every piece of feedback, and take your input very seriously.

Include my email address so I can be contacted

Saved searches

Use saved searches to filter your results more quickly

Name

Query

To see all available qualifiers, see our documentation.

You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session.

Dismiss alert

NuGet / NuGet.Client Public

Notifications You must be signed in to change notification settings
Fork 699
Star 769

Code
Pull requests 13
Security
Insights

Additional navigation options

Code
Pull requests
Security
Insights

Fix bug in the unique name generation for tools in the commandline clients#1627

Merged

nkolev92 merged 4 commits intodevNuGet/NuGet.Client:devfrom dev-nkolev92-toolsdeclarationwithnoversionNuGet/NuGet.Client:dev-nkolev92-toolsdeclarationwithnoversionCopy head branch name to clipboard

Aug 8, 2017

+80-12

Conversation Commits4 (4)Checks Files changed

Commits

Commits on Aug 8, 2017

Handle case, during the unique name generation, where there is no version in the tool reference
nkolev92
committed
add tests
nkolev92
committed
fix expected value in testS
nkolev92
committed
address feedback, use versionrange all instead of nulls
nkolev92
committed

Footer

© 2025 GitHub, Inc.

Footer navigation

Terms
Privacy
Security
Status
Docs
Contact

You can’t perform that action at this time.