This project is read-only.


Leading zero in package version breaks package restore in 2.7


Nuget 2.7 seems to have changed how it handles packages with leading zeros in their version, for example AjaxControlToolkit (

This package will install fine, but restore fails. Using fiddler to watch the request traffic, it appears that nuget is now dropping the leading zero in the version number when it is making api requests.

For example, the version listed in packages.config for AjaxControlToolkit after installing it is 7.0725, but as you can see from the attached fiddler trace, nuget is looking for 7.725, which fails.

This wasn't a problem with earlier versions of nuget.

file attachments

Closed Sep 18, 2013 at 7:26 PM by deepakverma
Verified it works fine after the fix.


JeffHandley wrote Aug 29, 2013 at 5:42 PM

Thanks for reporting this. Our best bet will be to fix this on the gallery. We have a work item there that I believe will address this.

I'll follow up with the gallery crew to ensure this scenario is part of that test plan.

cruikshj wrote Sep 12, 2013 at 2:23 PM

This is also affecting the latest version of Moq (4.1.1309.0919).

fujiy wrote Sep 12, 2013 at 3:21 PM

Will it be released before 2.8? I really need it

dotnetjunky wrote Sep 12, 2013 at 6:28 PM

Yes, hopefully we will release it before 2.8. For now, if you want to get the fix, you can download a build from our nightly build server at (use the guest account, and download the 2.7 release)