From our development roadmap, at this time there simply is zero interest amongst paying customers (or 98% of free users), so we can't justify the cost of building, documenting, and supporting this, given that we have a lot of other feature requests. However we'd certainly welcome help from the community in making ProGet Windows container ready; please let us know if you'd like to help!!

I think its now implemented: https://inedo.com/proget/versions 5.0.9

Looks like these symptoms are caused when the host goes OOM

Hi Giorgi, Are you using Windows Authentication for your instance of ProGet? Thanks, Jason

If you are using a newer version of MSBuild, see: http://blog.nuget.org/20170316/NuGet-now-fully-integrated-into-MSBuild.html If you are stuck with an older version, the solution is specific to whatever CI server you're using, e.g. with BuildMaster you would use the NuGet::Install-Packages operation; with TeamCity you would use the NuGet Installer build runner, and so on.

This is currently slated for ProGet 4.8-beta, which we expect to release in the next two weeks.

If you want to quickly add something like this are familiar with C#/.NET you can already create a custom package store to do this, see: Extending ProGet Beyond that, we will consider this as a first-class feature as you suggested. If you have any specific thoughts as to what would need to be configured for the hooks please add them to this thread.

Thanks for the quick reply! Ok, that's a shame but understood.

Hello Robert, Thanks for the bug report! I've filed this as PG-1047. NPM feeds were showing the download count as the total for all NPM packages, not just the ones associated with that feed.

Hi Alana This page (https://inedo.com/support/documentation/proget/core-concepts/connectors) has no info that I have to link the connector to my feed. Just add a little section at the end with a screenshot so the users sees what he has to do after creating the connector.

Hello Charles, upack pack expects a directory, not an individual file, so the command should be: upack pack C:\location_of_upack_json_file C:\directory_containing_my_setup_exe --targetDirectory=C:\mytargetDir\build_artifacts

Yes. Of course you will not be able to connect to NuGet.org as connector, or inedo.com for automatic updates and license activation. You can request a key from my.inedo and enter it in the installer.

Hello Tom and Brett, The endpoint being requested seems simple enough. For example, here's what it requests for -StartWith Inedo.. I've filed PG-1281 to add an implementation of this endpoint.

Never mind, found the 5.0 beta :-)

At this time we do not have a Go repository planned. This is the first request for a private Go package manager, and we have other ones ahead in terms of priority (PyThon, etc). But we will consider it for the future.

This is not a supported setting to change, and you won't find anything useful by changing it; it's only intended for diagnostic purposes when working with an Inedo engineer. The specific behavior may change from version to version, and we don't want to document how it works or support a particular behavior. if you're really curious to know, the best bet would be to look at the source code, and see how it's used; that's how we would use it ourselves.

You'll need to run bmdbupdate.exe. It doesn't need to be run on the database server itself; the user that runs it must have dbo permissions to the proget database.