Team System 2010 has some new features that really interest me including branched history, rollback, and baseless merge. Are these features available with just the new Team System Client, or do I have to upgrade my TFS server to use them?
You can do baseless merges in TFS 2008. Rollback is built into TFS 2010, but is also available in the Team Foundation Power Tools for TFS 2008. The new branch features are only available in TFS 2010 (you'll need to upgrade your server). The good news it that upgrading your server is fairly straightforward and there's an update for Team Explorer 2008 that improves its compatibility with TFS 2010.
Related
What are the best practices to migrate workitems say PBIs/Features manually from TFS to VSTS? And how to ensure we don't lose any linking to changesets or other linked child workitems?
Have referred the below link and the migration tool mentioned is deprecated and would like to know any other options which will help to migrate the data.
How to migrate work items from TFS to VS Team Services (VS Online)
The recommend way for now is using Migrate to Visual Studio Team Service, a way import your TFS Database into Visual Studio Team Services which definitely along with data.
However, currently only the following versions of TFS are supported for import with this tool:
TFS 2017 Update 3
TFS 2018
You may have to upgrade your TFS server to use. Alternative, the Microsoft official option is using public API-based tools.
Personally, even though Team Foundation Server Integration Tools has been deprecated. You could still use this solution in your case.
Besides, if you have no work item customization, then OpsHub is an
option. VSTS Sync Migration Tools is another way. But none offer a full fidelity migrations. Each tool has its own limitations.
We currently have a TFS 2012 Server which is being replaced by a 2015 server, the aim is to gradually migrate our code from one to the other.
When we do this we would like to maintain the checkin history, labels etc, Looking at similar questions the answer seemed to be to use the integration toolkit, however it looks like it (and its successor the integration platform) do not support TFS 2015.
We are using TFVC rather than git, if that makes a difference.
I don't have much knowledge about the integration toolkit, but I would actually suggest to do the upgrade one Team Project Collection at a time, but moving them separately to a new server with TFS 2015 installed. This way you will keep all history, label etc.
We have done this way back when upgrading from TFS 2010 to TFS 2013. Only obstacle that we had was a collection around 500 GB in size so it took around 16 hours for the upgrade to finish.
The following answer specifies the steps needed to move a collection to another server:
Copy TFS 2012 collection to another server with TFS 2015 Installed
We have used this Migration tool for our Client.
It’s possible to migrate TFS 2012 data to TFS 2015 with all information intact without any system downtime. The premium version of OpsHub Visual Studio Migration Utility (OVSMU) supports migration of projects with TFVC repository from one instance to another. It supports the 2010, 2012, 2013, and 2015 versions of TFS and all versions of Visual Studio Online, including the 2017 version. Along with basic data, you can migrate all workitems with history, comments, attachments, relationships, and source control with changesets, history, labels, comments, etc. You can checkout the details here: https://www.opshub.com/products/opshub-visual-studio-migration-utility/
Currently our team is using TFS 2008 and I need to substantiate my opinion to push my whole team forward.
What are the must-have features of TFS 2010?
Or: What are your main reasons to upgrade from TFS 2008 to TFS 2010?
Thanks in advance
Off the top of my head, these are what are important to me from a 2010 standpoint:
Hierarchical work items (parent/child)
Performance and Stability improvements
The concept of project collections to allow for logically separate instances of TFS to be hosted on a single data tier.
Ease of installation.
Better rollback support.
Better branching and merging visualization.
Improved process templates and reports.
Found an article on MSDN that describes all new jewels in Visual Studio 2010 Application Lifecycle Management
What's New for Application Lifecycle Management in Visual Studio 2010
We are using TFS 2008 for source code. The process template chosen was Agile 4.2.
I have installed VSTS 2010 to access TFS 2008 server.
Can someone please guide me on how to enable TFS 2008 with the ability to add Workitems - Test Case and Scenario into it.
You cannot use Microsoft Test Manager (also known as Visual Studio Test Professional 2010) with Team Foundation Server 2008. It requires implementation on the server which is not available in TFS 2008.
See Software Requirements for Visual Studio Application Lifecycle Management Features on MSDN:
To use Visual Studio Test Professional 2010, you must also install
Visual Studio Team Foundation Server 2010.
You can however create a Test Case and Scenario work item type in TFS 2008. This would just be a plain old work item form, no different to a Task or Bug like you already have.
Has anyone tried to integrate Tibco Designer especially for BusinessWorks with Team Foundation Server 2010?
At the moment, our Tibco designer is using VSS as its source safe control.
We are planning to migrate the VSS to TFS 2010 but I could not find a solution to integrate Tibco Designer with the TFS 2010.
I have no familiarity with the product directly, but since it is currently able to integrate with SourceSafe, perhaps the TFS 2010 MSSCCI provider might help?
You would install it on your client machine(s) so that application would be able to talk to TFS 2010 (and 2005/2008 with that version, it seems). I have used the provider for getting Visual Studio 2003 to TFS 2010, which does not have native TFS support.
Visual Studio Gallery Page for TFS 2010 MSSCCI Provider
Yes we have integrated Designer with TFS in a retail project, but it does not leverage full strengths of a source control system. There are no auto builds, trunking. Just basic check-in check-out. For Designer SVN is a recommended source control system.