Packages with leading 0 in version number are not well supported

I've already report this problem with STRING.FORMAT.JS 1.09

But if the workaround solution you give me was acceptable for STRING.FORMAT.JS which is a content only package, it's not acceptable for libraries packages

Takes for example the package Moq 4.2.1400.0717.

When installed through nuget.org the leading 0 is conserved on all the stack, in particular when creating the folder in the packages directory

however when using proget the leading 0 will be strip which create a folder name without that 0 in the packages directory resulting in a compilation error because the project is no more able to find the lib (for .\packages\Moq.4.2.1400.0717 do not exists)

I've tried some restore operation with proget as source and nuget.org as source, and cleaning all nuget caches between each test (in particular in "%userprofile%\appData\local\nuget\cache")

nuget.org always return a package including the leading 0 even if you ask for the version 4.2.1400.717
proget always return a package without the leading 0 causing troubles for compilation after restore and causing trouble during first installation because the nuspec inside the package still have the leading 0

I'm waiting for a real support, and rolled back our configuration files to use nuget.org instead of proget for public packages

Product: ProGet
Version: 3.3.10

We are testing a fix for this internally already, but as it involves a change in feed data, we wanted to be sure the fix didn't add any regressions for other versions. Since this is a blocking issue for you, we will work on getting a v3.3.11 out today with the fix.

v3.3.11 has been released that should resolve this issue.