Description
Description
paket does not search for 4-digit version numbers when a 3-digit version number is specified. Is this the expected behavior?
Repro steps
Steps to reproduce the problem:
-
I a package, SqlTableDependency: 4.1.1, and uploaded it to a ProGet server.
-
ProGet automatically appends .0 to make it a 4-digit version 4.1.1.0. (They said this is to comply with NuGet version 3.4 change for normalized version numbers: http://docs.nuget.org/Create/Versioning#Normalized_Version_Numbers.)
-
I run paket update and it I get this error message
Could not resolve package SqlTableDependency:
- Dependencies file requested package SqlTableDependency: 4.1.1
- Available versions:
- (4.1.1.0, [https:///nuget/])
Expected behavior
I was expecting 4.1.1 to work (not realizing that ProGet was changing it to 4.1.1.0).
Actual behavior
Specifying 4.1.1 fails to find 4.1.1.0 for the package.
Known workarounds
It works when I specify 4.1.1.0. (Is this the proper way to do it?)
Related information
- paket version 3.4.0 (or 3.4.0.0)
- possibly related ticket: Issue with paket and third party Nuget server when revision number is zero #1239