Integrated, so it uses the account hosting the web application to query.

To find the connector, go to Admin gear > Manage Feeds > Edit Feed (pencil icon), and that will have the list of connectors. For the error itself, try some of these recommendations: http://stackoverflow.com/a/703285

I see 2 boxes left (so around 30)

You can look in the Web.config file in the ProGet Service directory to see what connection string it is currently using to connect to the database. If you installed everything with default settings, this will be using integrated authentication, so it's connecting using whatever account the ProGet Service is running as. Outside of this, whoever installed/updated ProGet last would have also needed to have access for integrated auth.

This isn't currently exposed in the UI, but you can run this SQL query against ProGet's database to get a list of cached packages in a NuGet feed: SELECT * FROM [NuGetPackages_Extended] WHERE [Cached_Indicator] = 'Y' AND [Feed_Name] = 'MyFeedName'

Hi Mark, We just sent you an email with a stop-gap license. Please let us know if you don't get it.

This sounds like a bug in the specification. It was intended to work as you described - keeping 10 for each application, but it looks as if the actual specification is not that clear about it. I'm going to file this as a bug in the software, and we should be able to get it fixed in a maintenance release fairly soon.

Thanks, it works fine now :)

The self-hosted agent uses a proprietary binary protocol over TCP that is optimized for performance. IIS agents do indeed use SOAP over HTTP (or HTTPS). Both agent types can be secured using SSL encryption and client IP restriction. For an overview of how the agents differ, you might want to check out this article: http://inedo.com/support/kb/1039/comparison-of-buildmaster-agents

In theory, you shouldn't need to add a name unless there are multiple repositories for a single provider - if that's not working as you would expect then that is a bug. All of our test repos for multi-repo providers have a name, but it still seems to work without one. If it's easy enough to add a name as a workaround, that's the best bet, and we can update the provider again in the meantime as to not require it as before.

Hi, Thanks. I removed the extension and added it again. This time, it's version 4.8.1. :-)

That's actually supposed to be cached, but due to a bug it looks like it's only cached if there is not a timeout when trying to download the news. We'll get that fixed in a maintenance release; thanks for letting us know!

This is not a known problem on the server-side of ProGet, but instead a problem on the client; that "Stream" is referring to something opened on the client, and closed on the client. We've also seen similar behavior with some 2.8.x versions of NuGet.exe, and perhaps OD shares some of that code?

Can you try pointing the extension at the 32-bit MSBuild (or 64-bit if you are already using the 32-bit version)? Beyond that, have you seen: http://blog.nikosbaxevanis.com/2013/10/04/how-to-configure-msbuild-to-locate-the-fsharp-build-targets/

There is no "first-class" support for this framework, but anything that can be built/run with a command line can build/deploy applications that use it.

As long as the Global Catalog can search the other forest it should work, if there is a restriction on that, then it will not find the user. By default however, it uses the Forest.GetCurrentForest() to determine which GC to query. We are now planning to make some improvements to the way authentication works as it is slowly becoming the #1 requested feature/improvement.

This was fixed in ProGet v3.6.2, thank you again for the report.

That sound like a good solution!

Thank you very much guys for pushing this feature to the last release. I've upgraded our server today, turned the option on, and it works great. Cheers.

Sorry about the broken link! That article has be updated and that link should now redirect to the correct page: http://inedo.com/support/documentation/proget/feeds/nuget/visual-studio-extension