Thanks for the reply, this is exactly what I was looking for! I guess the piece I was missing was that there were additional permission options that aren't exposed by default, but that I could bring in by adding a new task. The links you provided helped me fill in those gaps, so thanks again for that!

Any updates on this? I encounter the same issue and none of your comments helped .

Please disable the "Overwrite Package" permission in Admin > Tasks. Then, you will get "Package Already Exists" error

This will be fixed with PG-1313

It's a "401" error, which means "not authorized" In this case, you could have the wrong credentials in Yarn (or no credentials). Note that "Windows Integrated Auth" is not supported by npm or yarn.

Hello Andre, The version number you posted is indeed a valid SemVer2 version number. If you go to the Manage Feed page for the NuGet feed, is there an orange button near the top of the page that says Migrate? If that button is present, the feed is not marked as supporting SemVer2.

I don't believe the NPM protocol allows for anonymous pushes. You could certainly have your CI put it in a drop folder however, which the ProGet would pick-up.

ProGet will not give this error code, so it's coming from another tool/service in between NuGet.exe and ProGet software. Please disable WebDAV, and any other things sitting in front of the ProGet server that would issue a 405 before relaying the request to ProGet.

Unfortunately, no, I was not. I'm in the process of taking a look at ProGet running in containers again, I will test in the near future and let you know. I don't expect it to be working unless something changed with the containers in the last several months.

Hi Ben, When trying with the universal feed API endpoint: I'm getting the error: So authorization is ok, but now it seems like feed API is waiting for a Key the extension is not sending.

There's a bug we haven't been able to figure out where the Linux version of ProGet doesn't respond to requests for URLs with colons in them.

THis is logged as a bug for [PG-758], and we may get this in next maintence release. Unfortunately it's a non-trivial fix.

Well i finally was able to publish to our Powershell feed. I updated the PackageManagement and PowerShellGet modules to version 1.1.0.0. which were released a few days ago... 12 Oct 2016 I hope this helps .

Ah yes, that solved my problem. Thanks!

I'm afraid we don't have any tutorials for this ourselves, but there a lot of third-party tutorails out there for using mvn. Here's one that might be helpful, directly from maven project:https://maven.apache.org/guides/mini/guide-3rd-party-jars-remote.html

Thanks! We will have this fixed in ProGet 4.0.14, which will be released within the hour.

The Build MSBuild Project actions effectively just run msbuild.exe against your project files; so, I would start there. KB1052 offers some troubleshooting tips, see the "Issues with third-party tools and integrations" section for how to dig into the details.

The discussion for this question is here: http://stackoverflow.com/questions/29254068

Yeah that's probably the best bet.

Reworking that page was already on our list of things to do for the next version, so this won't be an issue after that :) Thanks for your help!