That is indeed the correct behavior; the express edition is intended to make all users an administrator.

However, we are thinking of adding a new "mode" for express edition that will behave more like you desire: unauthenticated users will be able to view most everything, and authenticated users will be administrators.

In the mean time, why don't you just request an enterprise trial key? We understand that it can take while to totally prove out, and of course we will work with you to extend the trial key and help you prove the capabilities.

Hello; please fill out the contact form, and we will be able to you via email.

I see, that's an interesting idea. It seems like some sort of auto-generated documentation of sorts? I don't know if ProGet is the place for that data, but we don't have a feature to store such doumentation at this time.

So, maybe you could auto-post it a documentation wiki of sorts and use the "Project URL" property to link to it?

I'm afraid there's no easy answer for this.

First, keep in mind that dependency resolution is really complicated (see NuGet Docs to get an idea), and it seems some package managers (like npm) even have a nondeterministic (let alone undocumented) algorithm for resolution.

The only thing that "mostly knows" what packages are actually being used are the client tools themselves (nuget.exe, npm, etc), and you'll really only know what dependencies they've grabbed after you see the packages on disk.

ProGet has package statistics, which at least shows you which packages are being requested. But nuget.exe puts more information in the requests, so all ProGet "sees" is a request for a package from a address... and often, multiple requests happening in parallel.

Hello; this is not currently support in BuildMaster, but we may consider adding it.

However, it is already built-in to Hedgehog, which is more suited for lots of uniform style applications.

Unfortunately this is a bit tricky to give "general" advice on how to fix, but if you can submit a specific test case that we can reproduce as a ticket, we can research and try to reproduce it,.

The "remote icon" means that there is a package entry in a remote server. If you're continuing to see it, then it may take a little bit for the connector metadata (in memory)cache to be cleared. You could always stop/start the webservice, and then this will go away.

This should be cleared if you try the installer again

You can mirror ProGet feeds, but we don't have a Maven <> Maven repository option just yet.

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.

Are you using a "Legacy NuGet Feed" (created in v4), or is this a "new" (SemVer2) NuGet feed?

Leading zeros are no longer supported by Microsoft for NuGet packages, nor the ProGet SemVer2 feeds. So if you are still using them in your process, you really ought to change your process to use semantic versioning.

This is by design; accurately paging in the UI is basically impossible due to limited connector aggregation, package filtering policies, etc. Especially after you do a search.

Instead, you can display "up to 1000" packages in the UI, which is probably more than you would ever need to scroll through, and search as needed.

The error is "failed with: 401 Unauthorized", so it probably means you need to specify an authentication source?

We didn't change the way authentication is handled in v5, so it's likely unrelated to the upgrade.

I'm not too familiar with how OneGet fits into all this; you'd really be better asking this question at the Chocolatey or OneGet forum. You'll still use ProGet to host the packages, but I'm really not sure which client tool (choco, etc) will do the download and install on a desktop.

You'll want to use Chocolatey for this purpose; it's designed to install Windows software.

The PackageManagement module is intended for powershell modules for your PS runtime environment.

Both of them use NuGet behind the scenes, but we still recommend to create the appropriate feed for the type.

Just an update.. we have officially scheduled engineering resources to study/research/proof-of-concept a PyPi feed in late April (week of 23rd to be specific). Once that's complete, we will know exactly how easy or difficult it is.

Most likely, it will be very additive, and we won't need to tie it to a specific release schedule, as we could realistically include it in any maintenance release.

This is a results of network connections and traffic, and the message is coming from IIS or the ASP.NET hosting components. The server hardware itself is fine, but there's not enough network bandwidth to handle the load.

Keep in mind that your clients (NuGet, npm) will make hundreds (sometimes thousands) of simultaneous requests to the ProGet server to just a single "package restore". These requests are "expensive" and time-consuming, because often they'll need to check with a remote connector (which opens a new connection), backend database (network connection), validate security, etc. In addition, the workstations are typically more powerful than the server, so they will have more resources to make these requests.

So it really only takes a handful of users doing simultaneous package restores, and you are basically at a "denial of service" level of traffic. So, in this case, load-balancing is the way to do it.

This was introduced into 5.8; so please update to the latest v5.

https://inedo.com/buildmaster/5.8

Actually, the API isn't really any faster or slower.

If you find it faster to query NuGet.org's "v3" API endpoint, the reason is that it's a static index hosted on a massive Azure server farm. Your ProGet server is considerably less powerful. In addition, ProGet has connectors, authentication, package filtering, etc., and it would never be feasible or useful to generate a static index like NuGet.org does.

However, it is on our 2019 roadmap to implement this API, possibly as a new feed type or as an alternate API endpoint for an existing feed. But even so, if you need performance, you may still need likely need to stand up several ProGet servers in a load-balanced manner.

See How to Prevent Server Overload in ProGet to learn more.

The Integrated Web Server doesn't have many features, including request logging and tracking. So in this case, you'll want to upgrade to IIS:

Please refer to KB#1013: Hosting Through IIS Instead of the Integrated Web Server