Just a quick update -- we also fixed this in BuildMaster 5.0.4.

Please note a lot of these errors are coming from third-party tools, like svn or msbuild, so it's not possible to know precisely how to fix it without knowing more information. Unfortunately it's really difficult to diagnose or provide further troubleshooting with the information you've provided so far; if you paste/share the entire logs, we might be able to provide more insight. Please see KB#1052 - Troubleshooting Failed Builds and Deployments for more help on how to diagnose.

Thanks for the help... in the end I found I needed to install Microsoft Visual Studio 2012 Agents on the build server. The project was then able to build successfully.

There have been a few modifications since the version you're running to the symbol/source server that will likely fix the behavior you're experiencing. There is one issue in particular that involved reverse sorting of the symbol file's age value that I believe is related. When you upgrade to the latest, it should resolve the issues.

This error is coming from NuGet.org; unfortunately, certain long quriers will sometimes cause that error. It's intermittent. This is planned to be addressed with an "offline package index" in a future proGet release.

UPDATE: This is a breaking behavior change planned for NuGet 3.4. https://github.com/NuGet/Home/issues/2298 This may not have a large/widespread impact, and it might be difficult for us to fix server side without breaking everything other than NuGet 3.4... so for now our advice is "don't upgrade to 3.4 or don't rely on that behavior". Please update/share if this issue impacts you.

thx for the guidance

We removed that simply because it was confusing having both actions like that, your best bet is to use the Execute Command Line action, or a PowerShell script in the script library that does what you need.

Hi Matt, I would suggest to attach fiddler, and see what's going on. That XML you pasted is what a NuGet endpoint looks like; from there you can append /Packages to the URL, and see more of the exposed API.

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.

I'm afraid I don't have enough information to help diagnose this problem. Please keep in mind, BuildMaster isn't actually looking for anything -- it's essentially just executing a third-party tool like nuget.exe and msbuild.exe with the arguments you specify, so it's important to look at both the arguments to those commands and the working directories those commands are being run in. These will be logged near the top log for the action.

Hi, please refer to https://docs.nuget.org/create/creating-and-publishing-a-package and https://docs.nuget.org/consume/command-line-reference; just make sure to specify the ProGet URL for the --source option

Would love to see a VSIX feed (didn't see a way to vote for this feature).

You don't have to install Visual Studio 2015 on the buidlserver. Install MS Build Tools 2015 will do it. https://www.microsoft.com/en-us/download/details.aspx?id=48159

Here are the commands/switches that would be run ... https://github.com/Inedo/bmx-nuget/blob/master/CreatePackage.cs#L83]

Yes, most definitely. See KB#1072 - ProGet vs. NuGet.Server

Do you mean that some symbols are being indexed while others are not?

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/

VPN will occur at a much lower level than ProGet operations (which is HTTP/IIS), so I suggest you use a tools like Wireshark to dig a little further and see where the problem might be.

It's not recommended to check-in the modified assemblyinfo.cs file. For a few reasons, including the one you identified: it causes issues with source control related to the build. But moreover, attributes in AssemblyInfo.cs are metadata more than code; in other platforms (like Java) these are always added as part of the build process.