You will need to use Fiddler to determine the EXACT urls that are causing a problem during package restore; we can then investigate what query is causing the problem.

ProGet works great with NuGet client v3! As far as the "protocol" is concerned (i.e. ODATA vs JSON-LD) the "v3" protocol is intended only for use by nuget.org and nuget client. It's not documented by Microsoft, unstable, and they have no plans to document or support it. Since the "v2" protocol (ODATA) works just fine, we are not going to reverse engineer the "v3" protocol or otherwise use it.

The BuildMaster (primary) server currently only runs on Windows, but it can connect with MacOs servers via SSH. It's a web application, so of course you can access it on a Mac no problem.

I can't believe I missed that. I upgraded and that problem is gone but with new issues. Will open a separate question for that problem. Suggestion: How about adding a new tag npm? Thanks Niklas

If you're seeing this message, then you'll need to ensure ASP.NET4 is installed -- not just .NET4 and .NET4 Extensibility. It's a separate option (that's kinda hidden).

Embarrassing, a Spanish colleague had been on the server and changed all the setting!

Interestingly enough, disabling connection pooling for Buildmaster seems to have solved our issues. It's been five days and there hasn't been a single error in the event logs or Buildmaster itself. In app_appSettings.config we now have our connection string setting looking like this: <add key="Core.DbConnectionString" value="Data Source=localhost; Initial Catalog=BuildMaster; Integrated Security=SSPI;Pooling=no" /> Could this possibly be caused by a connection in Buildmaster not being disposed properly such that when it is pulled back out of the pool, it's in a broken state?

The basic process is: Install the exact same version of ProGet on the new machine Backup the ProGet the database and restore it onto new machine over the new database that was created by the installer Set a bulk import path for each feed Copy the packages from each feed into the corresponding bulk import path of each feed Allow a minute or so for the indexer to pick up the new packages and add them to the feed

Restarting the service sorted it thanks.

The current behavior is to never overwrite existing packages during a bulk import. Maybe we should add a configuration flag for this- at the very least I'll make a note to update the documentation to describe this behavior.

Hi Simon, If those buttons aren't lighting up, then the machine doesn't have internet access and can't request a key. Just go to my.inedo.com and request one instead, then enter it in. You don't need to manually install, but FYI that zip file would be in the manual installation package.

Apparently only the PowerShell scripts support variables in parameters and in scripts at this time, so we will have to add this feature for shell scripts as well. Ideally it will be included with the initial 4.7 release, but may be a maintenance release behind that. For now, if you use the Execute Shell Script action and enter the script as text or a file, it should work as you expect.

As currently written, I can't think of a good way to inject a connection string since that's handled at a higher level. I suppose the best way is to test against a local copy of BuildMaster with the connection string you want.

Hi Dan, we don't offer any additional pricing options; although we do provide licenses for free open-source projects.

Here is the "draft" list that will be posted on the website soon (Free, Basic, Load Balanced, High Availability): Features F B L H Unlimited Users X X X X NuGet Server X X X X NuGet Package Symbol Server X X X X Chocolatey Package Server X X X X npm Registry Server X X X X Bower Server X X X X Maven Server (beta) X X X X License Filtering X X X Connector Filtering X X X Feed-level User Privileges X X X Active Directory Integration X X X Package Retention Policies X X X MyGet Feed Synchronization X X X Package Statistics X X X Custom Licensing Agreement * X X Multiple Web Servers X X Multiple Index Servers X Automatic Failover X * w/ purchase of 5 or more servers

As far as I'm aware, this particular issue has already been resolved. Can you post a new question with the same details? For some quick suggestions though, does echo $ApplicationName work as expected? Is the application configuration to use new variable support (Settings -> Application Settings)?

Sorry to resurrect my old post, but I'm trying to use LDAP in ProGet and am running into the same issue. Users and groups that are in the domain of the server running ProGet are found, but users in a different domain are not.

Ah! That would explain why I couldn't reproduce this. I forgot that some versions of npm did weird things with URLs... Glad it's resolved!

That option unfortunately will not work at this time without significant changes, and it's supposed to be hidden currently. We may remove it in the next version or add the required functionality to get it working in an even later version. The problem with it is that dependencies can now vary based on other factors such as platform, .NET Framework version, etc. As a workaround, enabling caching for the feed and downloading the package from Visual Studio will accomplish essentially the same thing, though.

Please see: http://inedo.com/support/kb/1021/using-proget-with-nuget-the-visual-studio-extension