Please see http://inedo.com/support/questions/4360

I bumped into this issue as well. It turns out if you wanna use existing local SQL server, you need to add an account "NT AUTHORITY\NETWORK SERVICE" to your SQL database. To be clear, this account is added to ProGet database during installation but it didn't mark as "Public" in server role.

Unfortunately the behavior of Visual Studio's Debugging/Symbol Serving can be a bit strange; there's not much we can do to control that... however if you carefully follow the tutorial, it should help you get set up!

When I changed IIS to use ONLY Windows Authentication and then changed Proget to Integrated mode, all my problems went away.

Most definitely :) We don't have a target date just yet, but it's on our ProGet Roadmap. I'll add a +1 to the feature. Thanks.

In Chocolatey v0.10.1, we will automatically switch to using better TLS versions when available. This was done in https://github.com/chocolatey/choco/issues/458. If you see this issue when you are attempting to install Chocolatey itself, please see this documentation to understand your options: https://github.com/chocolatey/choco/wiki/Installation#installing-with-restricted-tls

this should be resolved in ProGet 4.0.8.

Hi, the package is superagent-mocker 0.3.0 fetched from registry.npmjs.org: see display in the npmjs.org : display of superagent-mocker 0.3.0 in npmjs org see display in proget

When I trying after remove all connectors, NuGet.exe install command works without any exceptions. :(

You do have to check the "remove the database and packages" options in the uninstaller, so if you did that it should have done just that, unless some error occurred or something like that. It's hard to say why things weren't removed in this case, but it's hopefully easy enough to manually remove if it didn't work. We'd rather there be a bug in not removing, instead of a bug in removing when you didn't want it to :)

Thanks!! Works like a charm

Dismiss my recent answer It works fine At some point the connector was removed from the feed which explains why nothing got listed even though the connector was fine. I'm really sorry for this! Thanks for the support!

Thank you for the report - this will be resolved in v4.0.7 due out later today.

Today it's working fine. So definitely a temporary outage on nuget.org.

Yes, please see the Get the Complete List of Connected Feeds Using the ProGet JSON API tutorial for a walkthru of how to use it.

Thank you for the report - this will be resolved in v4.0.7 which is due out later today.

RE: Retention Policies - those checkboxes are filters against the set of all packages, so if none are checked, then all packages would be deleted. Each checked box adds an additional restriction to or limits what would be deleted.

Caching is desigend to be transparent, so this is not currently an option. Of course there are a handful of ways to accomplish the behavior using a script, custom package store, package adapter via SDK, etc., would appreciate you sharing the method you use :)

Has .lib files been tested as yet? We are experiencing the same problem with the source server. Can we please get confirmation if this is supported?