-
Notifications
You must be signed in to change notification settings - Fork 525
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
Are NuGet package names case-sensitive? #429
Comments
BTW,
$ paket add nuget machine.specifications
Paket version 0.17.16.0
found: paket.dependencies
Adding machine.specifications to paket.dependencies <-- incorrect casing!
Resolving packages:
- exploring NUnit 2.6.3
- exploring Rx-Interfaces 2.2.2
- fetching versions for machine.specifications <-- incorrect casing
- exploring machine.specifications 0.9.1 <-- again
Locked version resolutions written to paket.lock
Downloading Machine.Specifications 0.9.1 to NuGet\Cache\Machine.Specifications.0.9.1.nupkg
Machine.Specifications 0.9.1 unzipped to packages\Machine.Specifications
Dependencies files saved to paket.dependencies
4 seconds - ready. diff --git a/paket.dependencies b/paket.dependencies
index 1855c60..aa95c10 100644
--- a/paket.dependencies
+++ b/paket.dependencies
@@ -1,4 +1,5 @@
source https://www.nuget.org/api/v2
nuget Rx-Interfaces ~> 2.2
nuget NUnit ~> 2.6
+nuget machine.specifications |
Yes there are still some places where have to use the corrected version name. |
forki
added a commit
that referenced
this issue
Dec 7, 2014
Fix casing issue in selective update - fixes #429
ghost
mentioned this issue
Oct 30, 2018
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Wrong casing,
nunit
:Correct casing,
NUnit
:nuget.exe
doesn't care about casing, but we apparently do:The text was updated successfully, but these errors were encountered: