Can someone explain the high level process, of installing TFS? I've had the Server set up by a "network guy". It's TFS 2010, and we're using VS 2010 and moving to VS 2012. Do I need to install something on my client machine, or does Visual Studio just "hook" into TFS automatically?
Also, I've been tasked with moving our VSS to TFS. I've seen those posts and don't need coverage of that, unless you wanted to point me to the best links of how to. When those instructions mention installing Team Explorer or needing SQL Server Express on the machine you are doing the migration on, do they mean my workstation or the Server?
The Microsoft walk-throughs are the worse (IMHO)...
well, I followed http://tfsguide.codeplex.com/wikipage?title=How%20To%20-%20Migrate%20Source%20Code%20to%20Team%20Foundation%20Server%20from%20Visual%20Source%20Safe
And nearly got it installed. I'll post a new question with the new issue.
Related
I'm looking to upgrade our internal source control from the archaic TFS 2008 on prem, to the nice shiny VSTS (was Visual Studio Online) however it really doesn't simple a simple process. I tried using OpsHub but it looks like TFS 2010 is the earliest supported there.
I'd be happy just manually copying code but I don't know of a way to maintain branch relationships once those branches have been put in to VSTS.
Can anyone point me in the right direction for how to upgrade/move my code?
I'd be happy with an answer that explains how to maintain relationships when copying branches from one version to the other
You can try with this tool: TFS Integration Platform.
I installed Visual Studio 2015 Enterprise RTM and only seeing "references" from Code Lens. We are using TFS for source control. I expect to see related commits from TFS. Based on this article, I have everything enabled in options:
Here is what I see in VS:
Is there anything wrong with my VS setup?
The TFVC lenses that are part of CodeLens only work when connected to a version of Team Foundation Server that is running the background job that generates the historical data. This means that you need to be running at least TFS 2013 or 2015 in order for this feature to work. Some features require a specific version of Visual Studio.
It is also possible that your server admin has disabled indexing on the server, one can do that using the tfsconfig codeindex command on the application tier.
A follow developer friend is trying to learn the TFS 2010 API.
We have established the following trial Virtual machine together:
http://www.microsoft.com/downloads/en/details.aspx?FamilyID=509c3ba1-4efc-42b5-b6d8-0232b2cbb26e&displaylang=en#QuickDetails
In our first test, we would like to read the set of bugs from a TFS project using C#.
Does TFS 2010 depend upon sharepoint being correctly configured on the server?
If so, is there an easy process for setting up sharePoint and relating it to TFS?
Any helpful direction you can offer would be greatly appreciated.
Wish you the best!
Just install sharepoint services 3 on the same server as TFS. It all works fine on a virtual server, I had it running with SQL and IIS on a VMWARE install with no hassles.
I am installing VSTS. What components do i need to install for both .net & sql server. ?
How do we configure our projects?
There are two parts to a successful Team System environment: Team Foundation Server and Visual Studio Team System.
For best results, install the former on a dedicated server. There are great resources to help you through installation right from Microsoft. There's even a video series of TFS-related content!
Once your Team Foundation Server (TFS) is installed, Visual Studio Team System (VSTS) is installed on your development workstation. VSTS looks just like any other VS install at startup. To configure it to work with your TFS instance, go into Tools > Options and Select Source Control: here you will see a pull down which should contain an entry entitled Visual Studio Team Foundation Server. I forget how to select your TFS server instance for VSTS to work with but I don't recall having trouble with it when I did it a few months ago.
Once you've configured all that, you interact with your TFS work items and source code from the Team Explorer and Source Control Explorer panes in VSTS: it should begin to feel rather like using VS without integrated source control from there forward.
The bigger issue is configuring your process in TFS to reflect your project's strategy, etc. That is an exercise in thought/reading more-so than how to configure it.
All this documentation is readily available via Microsoft's website. It does require some reading but devote some time to it: it'll pay off in the long run.
Team Foundation Server Requirements
We've planned to move from Visual SourceSafe to TFS. For this purpose, we brought a new server machine with updated specs and TFS installed. The Visual SourceSafe machine still has its use in the environment as the TFS machine dedicated for a single project.
All the projects are there in Visual SourceSafe machine and are being managed since more than half decade. As I said there will be only one project which is going to be moved on TFS machine. What we required here is a complete and safe image of VSS Working Directory of the project in TFS machine because to Migrate from VSS to TFS you would have to installed Visual SourceSafe there on TFS machine.
What is the best practice to move your
VSS Working Directory (project) from
machine-to-machine. Is there a way to
avoid this step and we could directly
move VSS Working Directory to TFS?
Once the project working directory setup on TFS machine, we can use VSSConverter.exe utility to migrate from VSS to TFS. There is an GUI version of VSSConverter.exe utility which makes this more easier than doing this through command prompt.
A Team Project is successfully created with MSF for Agile Software Development on TFS machine. There was an issue in the beginning trying to create the Team Project which seems SharePoint services were unable to start. Finally, we ended up on some blog who mentioned if you installed SharePoint Services after TFS then you have to check the SharePoint Central Administration Services and change its port to default 17012.
This is what we could have done on TFS. Not sure, are we on the right route or not? The ask is not big move a single project from Visual SourceSafe which is an independent machine to TFS machine. But, it is because we all are new on TFS.
The expenses already made, a new server machine, Windows 2008 Server R2, and TFS which let no choice for us except learn and do it. I hope this will become a good experience all in the end but to make it good we have to put more efforts and build attitude to get through this.
I will be thankful if you guys could suggest us on this circumstances how should we plan and collaborate. The best can be this, all this transaction will not affect our productivity on project. We could deliver and managed our deadlines along with this showdown.
Thanks.
Have a Good Day!
POINT 1: It sounds like you have already had someone recommend that you migrate all your projects at one time. The reason they recommended it is because it is generally a good idea. If I were you, I would take a second look at migrating all the projects and using switching everyone to the MSSCCI provider for TFS. This will essentially let everyone continue to work just like they do now and with the same tools they use now but the code will be in TFS.
POINT 2: Spend a little time to make sure you want to use the MSF Agile process template. Not because there is anything wrong it with MSF (it's great!) but because it is hard to change templates once you get started. This is the time you want to do a little thinking about software process improvement and how you want the office workflow to function once you are all using the full Team Explorer client. My shop has been using the Scrum for Team System template and we love it. It is especially cool when you add on the Scrum Dashboard web site and the Scrum Sprint Monitor on a publicly visible screen.