Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 6 years ago.
Improve this question
I want to move my TFS 2008 to Visual studio Team Services. Could you please tell me how to do that ? I saw few articles on this but it looks complicated to follow those steps.
Since TFS 2008 (and indeed 2010) is no longer supported you Will likely find it difficult to find documentation. There are two tools to help you. One from OpsHub that can migrate you to Team Services and the other from the product team called TFS Integration Tools.
You should follow the ALM Rangers migration guide if you can, and use the OpsHub tool if you can't.
Related
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 1 year ago.
Improve this question
http://msdn.microsoft.com/en-us/library/7cb80f0d-0119-4277-82e8-719a8db1796e
This is the link which was shared in a similar post some two years ago. However the link is not available anymore. Do we have an alternative.
If you want to migrate from VSTS to TFS on-premise, please see Migrate VSO to on premises TFS.
You can also have a try for VSTS Sync Migration Tools,it allows you to bulk edit and migrate data between Team Projects on both Microsoft Team Foundation Server (TFS) and Visual Studio Team Services (VSTS).
Then the alternative way would be get and upload the source code manually. And use Execl to export and import the work items.
Also, you can use OpsHub Visual Studio Migration Utility, the Commercial Edition supports migration from either TFS or VSTS to either TFS or VSTS.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 9 years ago.
Improve this question
I am about to start using Visual Studio 2012 Pro with Azure Websites. I am not using Source control at present. However the idea of rolling back previous versions is very appealing if new code does not work. I really want to keep this as simple as possible.
The options I see are:
1.) TFS (service)
2.) GIT from Local repository to Azure Repository.
3.) Hosted GIT. SInce I am not using GIT at present, then I think this could become an unnecessary extra step.
I am using MVC3, EF4.1, SQL Server, C#.
From your experiences of both, it would be very interesting to hear of your observations
Thank you in advance.
EDIT:
Yes it could be opinion based, but I was hoping for some factual feedback from any folks that had perhaps tried both. I have altered my question above accordingly.
You can use Visual Studio Online. It integrates well with Azure Management Portal and offers both TFS and Git.
Visual Studio Online is free for up to 5 users. Whether you want to go with Git or TFS, I suggest you play around with both and then decide which one you like.
It also offers Agile and Scrum development process templates.
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 10 years ago.
Improve this question
Currently our company is using TFS 2010 and TFS 2012 RC.
we need to upgrade TFS 2010 and TFS 2012 RC to TFS 2012 final on different server,
that already people are using the TFS 2010 and TFS 2012 RC environment.
I am not really sure what the question is here so I'll give you some links with information on the upgrade process. If you have specific questions, feel free to ask.
Upgrade guidance put together by the TFS Rangers: http://vsarupgradeguide.codeplex.com/releases
Official install and admin guides: http://www.microsoft.com/en-us/download/details.aspx?id=29035
A link to a book that covers the topic: https://www.smashwords.com/books/view/181289
The TFS integration project is what you want.
http://tfsintegration.codeplex.com/
We've used it successfully to consolidate two TFS 2010 servers with multiple project collections into a single TFS 2012 with a single project collection. It also provides two-way synchronisation so that a gradual migration of users is possible.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 5 years ago.
Improve this question
I'm thinking of giving each part of the agile lifecycle its own project (TFS project, not csproj) as per Microsoft's agile template.
Is it possible to move items (like User Stories or Tasks) from one Project to another?
Does the organization of these projects have any bearing on or affect the actual software build (solutions, csproj, etc)?
What is the recommended organizational structure of Projects, etc for an agile project?
Are there any guides you can recommend for setting TFS up to work with the standard agile process?
Do not set up multiple TFS projects for the same team/product line. You can't move things from one to another and they won't be able to share a common parent source control so you would miss out on much of what source control has to offer. Do some research by reading the links on the other answers.
I have never heard such a strange idea.
You should have one team project for each endeavor. Basically, a team project is the intersection of a team with a project.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 7 years ago.
Improve this question
Does it make sense to use the project management features of Team Foundation Server without using the Source Control and Automatic Build features? We're doing agile in an non-.net environment and would use TFS to manage the project but keep using the currently used source control and build software.
Thanks in advance,
One of TFS' primary strengths is that the work item tracking and source control are so closely linked. Another of its primary strengths is the integration into the Visual Studio IDE. It sounds like you wouldn't be using either of those features, so that starts to drive you away from using TFS as a solution.
Another factor that is an unknown here is how much you would need to pay for TFS licensing. If you already have that covered under existing MSDN licenses, then it probably isn't a factor.
That being said, the agile process template in TFS 2010 is a very nice agile-in-a-box solution, giving you the work items and management reports that you need to work in an agile environment. Additionally, you can modify the process template as needed to meet your particular flavor of agile.