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

This is by design; symbols work quite weirdly for native packages, and don't follow consistent conventions like .NET packages. So, we can't arbitrarily strip all .pdb files (we only remove them from the /lib path). In this case, we suggest to make a separate symbols feed.

Yep, you are awesome. I know this is an old post, but it was my issue as well. Using a nginx proxy for the server. Thank you.

With any versions of ProGet – from free to Enterprise – you’ll be able to access the repositories but scaling down from Enterprise to basic, or basic to free , you'll lose access to license filtering, feed-level user privileges, and other benefits that many users have come to enjoy, depend on, and take advantage of throughout their use of enterprise or basic ProGet. Very rare are there cases folks want to lose those features but if it's necessary, your team will still be able to access the repositories. Take a look at the full break-down of features and benefits per version here: http://inedo.com/proget/pricing/features-by-edition

Alright, well I did manage to make it work using IIS so at least there is a workaround, however since that was the only thing on that server that needed IIS it's too bad that I had to install and configure it only for that purpose. Thanks.

We have been running the update since it has been out and it does look like it has fixed our issues with random failing npm restores. Running my LinqPad test script now (which makes 32 concurrent requests for the same resource), still makes it "fail", but now with a 404 as you described, instead of returning an empty package. (Which is still quite weird behavior IMO...) Thanks for the quick response and help on solving this!

As far as I'm aware, the original issue in this thread has been resolved long ago. If there is a new issue with pulling connector packages, please post a new question.

Yes, but it's not "officially" scheduled as BuildMaster v5 is the top priority at the moment. Here is the roadmap for reference: http://inedo.com/proget/roadmap

We will explore this further; NuGet 3.4 added new abbrebrivations that we will be supporting in the next maintenance release.

Understood! Thanks for the quick response. Btw, it would also be nice to have a "Clear All" button in the recent errors section, because when we start having a ton of the same error, it fills it up and we can't clear them easily. Thanks again!

You might be getting that message if you have Windows Integrated AUthentication enabled; this is unfortunately not supported in the npm client. Otherwise if you follow the steps in the npm tutorial it should work just fine.

This seems to be unrelated; the problem before was that ProGet was not providing a 404 when a package was not found, but instead an empty result. Also, we cannot reproduce this error at all, so it's isolated to yours. As such, please Ask a New Question as not fill this one; and also make sure to provide a stack trace of the 500 error message; this can be found in Admin > Error Logs.

This would require creating an after-push adapter using the sdk. Several folks have done this in their own instances, but we currently don't hav ea tutorial for how exactly to write one;, but the classes should be fairly self-explanatory to assist with this.

Actually, reading your last sentence again, it sounds like I shouldn't use API keys in cases where I want to keep a feed secure. This is probably the best answer correct? Yes, pretty much. I suppose you could think of it as two different sets of doors that could secure a feed --- the first door (LDAP) is quite secure and can be user/group controlled, whereas the second door (API Key) is quite weak and works a bit like a skeleton key that everyone shares. There's zero point in requiring users to unlock two different doors, which is why we say using an API key doesn't make sense when you've enabled LDAP. If you want to use only an API key, then you must bypass the first door by allowing anonymous. This is less secure and generally not recommended.

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

Thanks, Tod, but I want to keep all the actions on the client side. I found that I can just do a GET and a PUT, and once I constructed the multi-part form data correctly and added a boundary to the content, it worked.

Connectors can only be filtered by ID, so you'll have to rely on the client to filter by pre-release versions. You can clear the cache on the Manage Feed page.

Hi, upack is the command line client for ProGet universal feeds. We will soon have it available to download from Chocolatey and Inedo.com, but for now you can find it directly at this URL: http://cdn.inedo.com/downloads/proget/upack1.0.0.zip

I'm afraid we don't have that tutorial yet; but we'd like to soon!

ProGet is the server, so it just hosts your private packages. If you want to push something to a different feed, use the -Source ... argument in the nuget.exe client. Connectors for NuGet are simply a convenience that make it easy to cache nuget.org packages and provide a single endpoint to download them.