Pushing VSIX Packages

[Jon McKee]

I successfully upgraded to ProGet 4.7.2 and set up a VSIX feed. I managed to manually upload a VSIX package, but I'd like to know if there is a way to automate or script the package upload.

Thanks,
Jon

Product: ProGet
Version: 4.7.2

[Dean]

It's a bug that this isn't documented, but you can PUT or POST a .vsix file to:

http://<proget>/vsix/<FeedName>

[Jon McKee]

Hi Dean, thank you for the quick response.

I tried posting the binary vsix file using the curl command-line client like this:

curl -D- -u Admin:Admin -X POST --data-binary @TsdLib.StarterKit.vsix http://proget:81/vsix/TSD_Vsix_Experimental

And I get this response:

HTTP/1.1 400 Bad Request Cache-Control: private Content-Length: 23 Content-Type: text/plain; charset=utf-8 Server: Microsoft-HTTPAPI/2.0 X-AspNet-Version: 4.0.30319 X-UA-Compatible: IE=edge X-ProGet-Version: 4.7.1.4 Date: Tue, 21 Feb 2017 21:35:27 GMT

Invalid version number.

[Dean]

Appears to be another bug. Probably why this hasn't been documented yet :)

You may be able to work around by adding a name+version to the url, such as:

http://proget:81/vsix/TSD_Vsix_Experimental/rubbish/1.0.0

It shouldn't even matter what you use, it could literally be the values in that example, as long as there's a name and version number. In any case, we'll have a fix in v4.7.3.

[Jon McKee]

Hi Dean, I tried adding the /rubbish/1.0.0 to the end of the url but now I get a the 404 response code, with Unknown API endpoint message.

[Dean]

This is now fixed in v4.7.3.

[Jon McKee]

Thanks Dean, upgrading to 4.7.3 has solved the issue!