tfs2010

There's not much more to add really than the above question. I have a fairly simple build process template, which has hardly deviated from the default one. I have two custom activities, which by recommendation live in a separate assembly within the same solution. However.... Opening the template takes about two minutes. Changing properties on an activity in the workflow, reordering activities in the workflow, adding activities to the workflow, all take between 30-60 seconds. It's completely unusable at the moment and I'm beginning to regret moving from Cruise Control to TFS for build

I have just branched from Main to v5.0 but I realized that I want to move this branch inside the Release folder. How should I proceed with TFS 2010? Thanks. Simply right-click on your branch in Source Control and select 'Move..'. Set your desired destination path, and commit this change. You should be OK. I think I 've read somewhere that moving folders & renaming folders shouldn't be done in separate steps, so if you plan to also rename your branch, do this in a next step. Once you 're done, you should check that with right-clicking MAIN > "branching and merging" > "merge..." you have a

We are using TFS 2010 and facing a problem with deleting a folder inside of a solution in Visual Studio. In the latest version of checked-in code, the directory in question has files in it. One of the developers decided to move the files in that directory to another location within the solution. He then tried to delete the old folder but go the following error: This operation cannot be completed. You are attempting to remove or delete a source-controlled item where the item is either exclusively locked elsewhere or otherwise unable to be deleted from source control. Does anyone know what the

As far as I know, Team Foundation Server 2010's source control (and prior versions) doesn't support linking (Symbolic links) of files. Linking (per Visual SourceSafe) was the concept of providing one "hard" file in a folder, and then "linking" to it in other locations - exactly like file system hard links are designed. Does anyone know if files can be linked at all? I realise it is not a good practice in general, but I have some scenarios where it makes sense. According to an answer in this thread: Linking TFS source control folder from another TFS project it's not possible, but I can't find a

I downloaded and installed the new Team Foundation Server Scrum v1.0 beta work template from Microsoft. I would like to edit the drop-down that displays in the Iteration field used when entering a new Sprint work item. If I enter in a release / sprint number that does not exist I get the following message: "New Sprint 1: TFS20017: The area or iteration provided for field 'Iteration Path' could not be found" Does anyone know where I need to go to edit this listing? Thanks! Connect to TFS. In the Team Explorer, select the team project you want to define the iterations for. Click on the Team menu

In the TFS Branching Guide 2010 v1 ( here ) the ALM Rangers gives you 4 branch plans (scenarios) at the moment. But in a related project, TFS Guide, also from the ALM Rangers ( here ), they offer a scenario "No Branch". This is good starting point, because having for example 2 branches (dev and main) will slow down the velocity and does introduce more complexity because of all the FI (forward integrate) and RI (reverse integrate) handling. It looks for me that ALM Rangers do not sync both projects, because the branching guide 2010 v1 is not offering the "No Branch" plan anymore.... For our

This question is similar to: Find in Files: Search all code in Team Foundation Server However it was asked 4 years ago. I'm asking specifically about TFS 2010 with VS 2010. Has Microsoft finally got around to adding back the searching of files for code snippets like they had way back in Visual Source Safe? If so, how to enable it and use it? I've tried adding in Microsoft's Power Tools. While it has a search feature, the search is only for file names and ignores looking in the content in the files. :( Craig I had the same problem and found this thread whilst looking for the solution. I then

Using TFS, we have the following: A main baseline A development branch for each development effort. These get merged back to the baseline. A release branch that is created with each release. Bug fixes are made here, released, and merged back to the baseline. Using shelvesets, we can share code across development branches if needed without contaminating the baseline. Useful for code reviews. When we deliver our development changes to baseline we have an automated build that kicks off and automatically places our changes on the test server. The problem is that the business analysts can't see our