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

Yes, all of our the free/express versions of our products allow for commercial use! Thank you for your interest.

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.

Hi Stephen, Although we don't offer reseller discounts, we are happy to (and often do!) work with any software reseller. If you have an approved reseller on your list, chances are they have already purchased from us before... and if not, we make it very easy. They can just submit a purchase order to us (or start by requesting a formal quote), and we will go from there. Does that help? best, Alana

Believe me, we really wish it was feasible to provide "Integrated Windows Authentication" (i.e. 401/NTLM challenges) for some feeds, and "Anonymous" for others. The problem is that this is implemented at the HTTP.SYS stack level (a kernel-level service), which far below IIS. NTLM/Kerberos authentication is not something we can feasibly implement ourselves... even if we did, the TGS Exchange cannot really run in a protected environment (like an app pool user). This has been a known issue by Microsoft for at least 10 years, and they are planning to introduce some new libraries/options with Server 2016. There are rumors they will drop it altogether in favor of federated authentication (i.e. Azure style). But, it's not huge on their priority list I think.

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

npm does not support Windows Auth. Unfortunately IIS/ASP.NET does not allow for some things to be Anon, some things to be Windows -- the whole site is one or the other. Best workaround is to create two IIsSites on the site server with different ports. You can point both of them to the same application directory. Note this does not require a separate license because it's considered the same instance, and largely a workaround for the authentication problem.

We're still working it... currently there are some issues surrounding the .NET 4.5 implementation in the Mono distribution, which we hope to see resolved soon!

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

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!

Thanks!! Works like a charm

Yes; the JSON-based REST API allows you to do everything you can from the website, and there's also a simplified job trigger endpoint, where you can do something like POST /api/jobs/trigger/mytemplatname?key=secret123 to trigger a new job. These particular bits aren't fully documented (or implemented in current the v1.0 release) yet, but will be in just a day or so.

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 :)

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

Thank you for the report - this will be resolved in v4.0.7 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.

FYI one of our developers posted an answer on the linked question.