tfsbuild

When I try to queue a build on my on-premises TFS 2015 Update 1 I get the following error message: No agent could be found with the following capabilities: grunt I've already installed NodeJS and grunt-cli and they're in the path (i.e. they can be executed in cmd from any location). What am I missing? Go to your pool settings page: http://SERV_NAME:8080/tfs/_admin/_AgentPool and select your agent, verify that grunt is added as a system capability with the correct path set. If it's not there, you can manually add it as a user capability Something recalculates the system capabilities but I'm not

I'm using Pre-/Post-build events in my VS2012 project files to perform build tasks. This works perfectly fine locally, but I have an issue running it from our TFS 2012 Build Server. Locally the $(TargetDir) for each project is set to its own /bin folder. On the build server however this is set to a single /bin folder outside of the solution root folder in which it consolidates all the binaries that were build. This is not at all what I want! I just want the build server to behave the same way as my VS2012 build does . There doesn't seem to be any setting in the build template that allows me to

I'm trying to migrate from TFS 2012 Update 2 to TFS 2013. Following the documentation I installed TFS 2012.2 on the new hardware, backed up/restored the databases, then installed TFS 2013 as an upgrade. I can see the Team Project and the builds. The problem is when I right click a build to queue up a new one and click on the Parameters tab I just get a blank panel. My best guess is there was an error loading the parameters. Note those builds worked fine in TFS 2012.2. If I create a new build from scratch and I use their new default template (TfvcTemplate.12.xaml) I still get the same error. I

I am getting below error, while execute build in TFS 2010: C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Microsoft.Common.targets: The reference assemblies for framework ".NETFramework,Version=v4.5" were not found. To resolve this, install the SDK or Targeting Pack for this framework version or retarget your application to a version of the framework for which you have the SDK or Targeting Pack installed. Note that assemblies will be resolved from the Global Assembly Cache (GAC) and will be used in place of reference assemblies. Therefore your assembly may not be correctly targeted for the

We Have a large VS solution using project references which is build by TFS Build like so: Solution - Project 1 - Project 2 - Project ... - Project N Because the solution is too large we have several smaller solutions which we use day to day: SubSolution - Project 1 - Project 19 The problem is that developers working on SubSolution find that it is not building because the project references could not be found, so they change the projects to use file references. This then goes on to break the TFS Build which cannot find these file references because they have not been built yet (Even though the

I want to exclude some tests from my continuous integration build but I haven't found a way to do so. One of the things I've tried was to set up the priority of those tests to -2 and then on the build I specified Minimum Test Priority = -1 but it still run those tests. Any help would be greatly appreciated. Instead of using "Test Lists" that have been described, you should use the "Test Category" method. The test lists & VSMDI functionality have actually been deprecated in Visual Studio 2010 and Microsoft may remove the feature completely in a future version of Visual Studio. If you'd like

TFS 2013 - Build: ASP.Net 4.5.1 website I get this error: warning MSB3268: The primary reference "C:\Builds\2\MyProj\Web1_Main\bin\MyProj1.dll" could not be resolved because it has an indirect dependency on the framework assembly "System.Runtime, Version=4.0.10.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" which could not be resolved in the currently targeted framework. ".NETFramework,Version=v4.5.1". To resolve this problem, either remove the reference "C:\Builds\2\MyProj\Web1_Main\bin\MyProj1.dll" or retarget your application to a framework version which contains "System.Runtime,

As part of our ASP.NET Core 2.0 build process I have added a dotnet test command which I have added as a Windows batch file. Here is my command. dotnet test "MyProject.csproj" --no-restore --results-directory "MyProject\TestResults" --verbosity minimal And here is the output when run from the command line. So it all appears to work correctly, yet no test results / test output is created. Andy Li-MSFT To output the test results from dotnet test, you can try pass -xml /some/path/out.xml or use the work parameter, like this: dotnet test --work:"mypath/myresult.xml" . See below threads for details

I've been trying to setup my build server (Team Foundation Service) to automatically download 3rd party libraries and successfully build, but I don't know how to do this. Is there a way ? Radoslav Minchev you need to enable package restore for the solution you want to build on the build machine. This is at least what I did to get NuGet to work with Team build. Here's a link about package restore and how to use it during build http://docs.nuget.org/docs/workflows/using-nuget-without-committing-packages To build upon what John Korsnes says above in his comment (because that alone wasn't enough