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

Thanks; we've identified a possible race condition during initialization, specifically involving discovering the connection string of the currently installed instance. We've made a small code change which should resolve this issue - assuming it is the cause. We haven't been able to reproduce it on our systems. The installer for the next version (which should be 3.6.2) will have the fix, so you may want to try using the larger installer again just to see if the issue goes away. You never need the full installer to perform an upgrade, however.

Thanks for the help investigating this. We've identified a possible race condition during initialization, specifically involving discovering the connection string of the currently installed instance. The presence of .NET 2 shouldn't affect things, as the installer specifically targets 4. The 20 in the CLR20 error just refers to the runtime version. .NET 4 runs on the CLR 2.0 runtime, confusingly enough. We've made a small code change which should resolve this issue - assuming it is the cause. We haven't been able to reproduce it on our systems. The installer for the next version (which should be 3.6.2) will have the fix, so you may want to try using the larger installer again just to see if the issue goes away. You never need the full installer to perform an upgrade, however. Again, thanks for the help!

Hmm, we'll have to look into that... Just use Applications_PurgeApplicationData with this method: http://inedo.com/support/tutorials/cloning-an-application-with-the-sql-api

Most definitely not. Unfortunately, we have no idea when NuGet v3 will come out, nor do we know when/if there will be API docs availalble (or a stable codebase to reverse engineer the API). Based on the various iterations of the v3 API that have been published in preview/beta, we have little confidence that it will solve the performace problems that ProGet users experience with connected/remote packages; so, on the ProGet Roadmap, we plan on solving that by creating a full index of nuget.org. That said, the NuGet team will need to support v2 for several years to come, so we're in no rush. Moreover, We have a plan that http://inedo.com/support/questions/3130

See: http://inedo.com/support/questions/3090

Also for convenience, as of .NET 4.0 there is a CopyTo() method on Stream that will do the buffering for you, so you can just call: srcStream.CopyTo(destStream);

Retention Policies are not inclused in the free edition. You can still delete packages manually however.

Turns out it does work, there was another issue preventing it from running. What's got me confused though is that the script is being run from the SRC directory (that's what the unix pwd command implies) when it was copied to the WRK folder as you can see from the log. Downloading http://192.168.59.103:8081/artifactory/libs-release-local/myapp/0.1/33/trial.sh artifact to C:\BuildMaster\_SVCTMP\trial.sh Transfer C:\BuildMaster\_SVCTMP\trial.sh to /tmp/buildmaster/_A5/_S5/WRK/trial.sh over SSH Execution complete. Finalizing... Target directory used. Abandoning source. Finalization complete. Source and target directory are the same; splitting... AgentBasedAction initialization complete: Temp Directory: /tmp/buildmaster/_A5/_S5/TMP Source Directory: /tmp/buildmaster/_A5/_S5/SRC Target Directory: /tmp/buildmaster/_A5/_S5/WRK Server: DockerVM (Id: 2) Initializing action... Initialization complete. Executing... trial.sh /tmp/buildmaster/_A5/_S5/SRC Script returned: 0 Script completed. Execution complete. Finalizing... Target directory unused; joining with source. Finalization complete. Source and target directory are the same; splitting... AgentBasedAction initialization complete: Temp Directory: /tmp/buildmaster/_A5/_S5/TMP Source Directory: /tmp/buildmaster/_A5/_S5/SRC Target Directory: /tmp/buildmaster/_A5/_S5/WRK Server: DockerVM (Id: 2) Initializing action... Initialization complete. Executing... echo result: Hello World, we've made it! ls result: trial.sh pwd result: /tmp/buildmaster/_A5/_S5/SRC