tfs2013 | 易学教程

Which version of VS should I install to allow unit testing on the build server?

阅读更多关于 Which version of VS should I install to allow unit testing on the build server?

问题 Since a few weeks we have our first TFS (2013) setup. The setup is rather small and there are only a handful (read: 10) developers that will have to work with it for the time being. It was setup as a "test" to see if it fits within our organisation. Now, we'd also like to test the build server functionality. We've configured the build server and enabled a single agent. The MSDN then states that "You must install on the build agent the version of Visual Studio that your team uses on its dev

how to undo pending changes of files that are unchanged?

阅读更多关于 how to undo pending changes of files that are unchanged?

One thing that drives me crazy with TFS is the fact that if you have a file checked out, but you made no changes to it, it still shows as a change, distracting you from real changes that you made. This is especially annoying when you use tools such as T4 to generate code, because most of the time the tool will generate the same code, but will leave the file checked out. For some reason that I can't understand, Visual Studio insists in showing those as changes, and will even claim that there are conflicts if another person happened to check-in the same "changes". Fortunately, the TFS Power

TF900547: The directory containing the assemblies for the Visual Studio Test Runner is not valid but can't see MSTest.exe

阅读更多关于 TF900547: The directory containing the assemblies for the Visual Studio Test Runner is not valid but can't see MSTest.exe

问题 I'm getting the following error on a TFS2013 build: TF900547: The directory containing the assemblies for the Visual Studio Test Runner is not valid ''. Looking here, it would seem that the answer to this is to change the test runner from VS test runner to MSTest. However, when I try to edit the Test Run in the build definition, the test runner option is set to Visual Studio Test Runner and greyed out. What determined what is shown in this box, and how can I add MSTest? I have installed

TFS 2013 event handling on work item change

阅读更多关于 TFS 2013 event handling on work item change

I would like to develop software which runs every time a work item is being created or changed in a TFS team collection. My TFS server version is 2013 and i'm planning to upgrade soon to 2015. I tried the following article but it doesn't work on 2013... What do you recommend? Found the answer! here's my code: using Microsoft.TeamFoundation.Common; using Microsoft.TeamFoundation.Framework.Server; using Microsoft.TeamFoundation.WorkItemTracking.Server; using System; using System.Collections.Generic; using System.Diagnostics; using System.Linq; using System.Text; using System.Threading.Tasks;

What are “Excluded Changes” in Team Foundation Server?

阅读更多关于 What are “Excluded Changes” in Team Foundation Server?

问题 When I check in changes in TFS Express 2013 using Visual Studio 2013 Professional, there is a list of "Excluded Changes" that has 1541 items in it. I have never told TFS to exclude a change, and do not understand why anyone would even want to "exclude" a change (isn't source control all about SAVING changes???). I am a bit worried that I have changes that are not being saved...but am even unsure if this is even what it means. I have Googled for more information about "Excluded Changes" in TFS

The directory containing the assemblies for the Visual Studio Test Runner is not valid

阅读更多关于 The directory containing the assemblies for the Visual Studio Test Runner is not valid

We have upgraded our TFS installation from 2012 to 2013. When running our builds they will fail with the following error if unit tests are enabled: TF900547: The directory containing the assemblies for the Visual Studio Test Runner is not valid '' The build process template or build definitions has not been changed after the upgrade. The upgrade process did not change them. Where can I provide the path to the Visual Studio Test Runner and where is it located on disk? I do not know if "Visual Studio Test Runner" is a new option for 2013 or if this setting was also used before, when we were

What is NOT supported in TFS 2013 Git mode from what is there for TFVC?

阅读更多关于 What is NOT supported in TFS 2013 Git mode from what is there for TFVC?

问题 Recently I realized the fact that not all functionality available for TFVC is supported for Git-mode projects in TFS 2013. This has been indirectly proved by the blog post of Brian Harry, saying: ...we are fully integrating Git into the TFS ALM workflows – work item tracking, build automation, reporting, code review, and more. Not all of that integration is complete yet but we’ll be fleshing it out through the 2013 Updates and, when we are done, we should have full parity on ALM integration

How to remove Sharepoint and Reporting Services from TFS 2013?

阅读更多关于 How to remove Sharepoint and Reporting Services from TFS 2013?

问题 We’re running TFS 2013 Update 1 and I’m planning an upgrade to TFS 2015 Update 1. We have both SharePoint and Reporting Services installed and configured for TFS that I like to remove, because nobody ever uses them. So, do I simply uncheck both Reporting and SharePoint during the TFS 2015 upgrade wizard. Is this the best way to do it? Or, do I un-configure Sharepoint and Reporting Services first from our TFS 2013 installation? If so, what are the steps to do so? Environment: Server computer A

Git submodule fails on TFS Build

阅读更多关于 Git submodule fails on TFS Build

When I try to build using TFS with Git, there's a limitation whereby TFS's git provider doesn't yet support sub modules. Bit of a pain, but what the heck, I'm able to tell TFS to run a Batch file prior to compilation. I've used this to call a manual git script to update all my submodules in my "super" project. The command this batch file runs is simply: git submodule update --init --recursive This worked fine and dandy before I migrated the submodule source to TFS, however now the TFS build is failing, because the above git module script no longer works. So, what TFS does before a build is

Code Review before checking in to TFS 2013

阅读更多关于 Code Review before checking in to TFS 2013

I'm trying to implement a process so that the manager can Review the code of all developers before the developers can check in to TFS 2013. Is there any process to require a review of the code by a human being before it is added to a real project? I'm using TFS 2013 with Visual Studio 2013. TFS 2013 supports this out of the box, and is very straight forward to use. Developer needs to file a request for review in the team explorer: Go to Team Explorer Open pending changes Under "Actions" menu, choose Request Review Specify the reviewer, and send. The target user (in your case, the manager) will