Proget ChocolateY-feed and ChocolateY naming conventions don't play well together.

I am experimenting with using ChocolateY as a deployment mechanism for our internal software.
I have created a ChocolateY feed on our proget server, and added a couple of packages:

arenaframework-client 0.0.1

arenaframework-client 0.0.2

chocolatey 0.9.8.27

First, I ran "cinst arenaframework-client -version 0.0.1"
This runs without a hitch, the package gets installed. Great success.

Given that I have v0.0.2 of the same package, I then tried to run "cup arenaframework-client"
This should update my package to v0.0.2, but returns with "nothing to update"

Having digged into the powershell modules that makes up ChocolateY, I found that it uses "nuget list" under the hood to find updates to a package.

So, this is the root of the problem:
"nuget list" (without any parameters, from the command line) returns:

arenaframework-client 0.0.2

chocolatey 0.9.8.27

"nuget list chocolatey" returns:
chocolatey 0.9.8.27

"nuget list arenaframework-client" returns:
No packages found.

So it would seem that the hyphen in the package name is something that Proget doesn't handle.
However, the hyphen is part of the recommended ChocolateY naming convention.( https://github.com/chocolatey/chocolatey/wiki/CreatePackages )

Any recommendations on how to get around this problem would be greatly appreciated.

Sincere regards,
Erling Paulsen

Product: ProGet
Version: 3.1.7

Thank you for the report. It turns out if the package title is different from the ID, only the title is searched for the list command. We have fixed this on the ProGet end to search both ID and title regardless of difference and are planning on releasing v3.2 today which will include the fix.

You could also hack that chocolatey script to use nuget list id:arenaframework-client which should work with the version of ProGet you already have.