My team is moving to TFS 2010, but all of our old projects are from our stand alone VS 2005 and VS 2008. We did not have Team Server. Can put our projects under source control in TFS 2010 without upgrading and migrating them?
If you don't want your VS 2005/2008 projects upgraded (most likely VS 2010 will only touch the solution file), then you can install
this for VS 2005 (allows you to connect to TFS 2010 from VS 2005)
http://support.microsoft.com/default.aspx/kb/979258?p=1
this for VS 2008
http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=cf13ea45-d17b-4edc-8e6c-6c5b208ec54d
No, you need to migrate them using VSSConverter. Another option is to simply keep the old VSS2005 in play and switch Source Control as necessary in VS.
Related
I have been looking for solutions to providing source control for my SQL Server 2012 instance. I have looked at Red-Gate's solution but it is outside my price range. Since I already make use of Visual Studio Online (VSO) source control for my .NET projects I was wondering if it was able to provide source control for SQL Server?
I have seen articles (listed below) that discuss using Team Foundation Server (TFS) for source control however I do not have a dedicated TFS server, just VSO.
Use Team Foundation Server (TFS) as your Source Control in SSMS
Using the TFS as a source control repository for SSMS projects
Has anyone made use of VSO to handle source control for their SQL Server database?
I would definitely recommend using Visual Studio Online or Team Foundation Server to hold your database scheme in version control. There is a fairly recent article in Visual Studio Magazine that discusses using the SQL Server Data Tools (SSDT) to be able to make that easier for you: Simplifying Development with Visual Studio Database Projects. SSDT is available for any version of Visual Studio including the Community and Express editions.
Redgate was out of my price range too unfortunately...
The SSDT tools for VS are amazing, and i recently started using it for comparing DB versions - and then generating change scripts.
Here's a start point if you want to get into that...
Other Free Alternatives?
Liquibase
gitSQL
Liquibase - i couldn't get my head around but if you can get it working, it may be better for other databases, if you have the requirement to use other databases.
I use gitSQL - it's free up to 20 tables...
If you have more than 20 tables then it costs $40 - which is still so much cheaper than the redgate solution.
gitSQL are also setting up command line options in a future release, so potentially you could run it via a batch file, and set up continuous integration.
gitSQL are also talking about postgres, mysql editions in the future.
I want to migrate all the source code from a TFS 2008 server to a new installation of TFS 2010. There are no work items, reports or portal to migrate, only source code. We want to move to a new process template and don't want to make an upgrade of the template used in TFS 2008 projects. Are there any good tools to only migrate source code? I've done some tests with TimelyMigrations TfsToTfs but they don't seem to work well when migrating a lot of source code.
Has anyone tried to use Team Foundation Server Integration Tool? I suppose you need to upgrade the TFS 2008 to TFS 2010 before you are able to move the source code to a new TPC/TP with the process template we want to use (with fresh portal and reports). Is this correct?
I have Microsoft Team Foundation Server 2008 installed on my company since tree years. I installed TFS 2010 and I want to migrate the version control from 2008 to 2010.
I tried to use Team Foundation Server Integration Tools (March 2011 Release) but I've got an error/conflict when I tried to migrate:
The target server http://tfs2008:8080/
is not a TFS2010 server
I don't know why it says target and not source even I've putted it (tfs 2008) on the left source!!
Can anyone any idea what's going on?
Thank you and Kind Regards.
I was able to migrate from the tfs 2008 server, I ran the TFS integration tool from 2008 and it worked.
This might sound like a silly question but is there a manual or a guide on how to set up Team Foundation Server 2010 in Visual Studio 2010 Premium or Ultimate? It comes built-in right?
I've only got up to the Server list part. It's asking me to select a TFS server and port, but I don't think I have one. All I have installed is Visual Studio 2010. According to this product comparison page, TFS 2010 should come pre-installed with Visual Studio 2010.
Team Foundation Server is the source control server application. It is not the same as Visual Studio 2010 Premium/Ultimate.
In order to use TFS, you must install it on a machine on your network, then connect to it using the client, which is what comes preinstalled with Visual Studio.
Back in 2008, you'd have to download the TFS Client separately and install that in order to connect Visual Studio to a TFS instance. This might be what's leading to your confusion.
No, it doesn't come built in. Team Foundation Server is a separate product from Visual Studio; the (slightly misleading) table on the page you linked does indicate that TFS "can be purchased separately."
I have been looking for a way to migrate and upgrade our TFS 2008 server to 2010 server preferably without losing any data.
I have been looking at the TFS Integration Platform
http://tfsintegration.codeplex.com/
and also Visual Studio 2010 TFS Upgrade Guide
vs2010upgradeguide.codeplex.com
Looking at the document TFS Integration Platform - Migration Guidance.xps using the first link, it seems to suggest that I could preserve all the data by first migrating the TFS 2008 from one server to the other and then upgrade the TFS 2008 to 2010.
Is this true?
Thank you,
Chen
Chen - We just went through this process a few weeks ago. While it's not a trivial matter it can be done. There is actually specific guidance for an upgrade with migration to new hardware in the TFS Install Guide. Take a look at the Scenario: Upgrading Team Foundation Server section and the sub-section named Checklist: In-Place or Migration Upgrade on One or More Servers.
The most challenging part of the exercise for us was the SharePoint setup/configuration, but if you follow the guide closely it should go fairly smoothly. This post may help with the SharePoint piece.
If the database is on its own box then you first need to upgrade to SQL 2008. Once that is done you can install TFS 2010 on a new server, select upgrade during the install and point it to the database server.
If the database is on the same box as TFS 2008 then you first need to backup all the databases and restore them on to the new box with SQL 2008. Then install TFS 2010, choose upgrade during the install and point it to the database server.
It should be. Migration of 2008 from one server to another is primarily a database exercise, but it can get tricky when you are initializing the Application Tier.
To be honest, I thought the TFS Integration Platform migration was providing guidance around moving from TFS 2005 to TFS 2008. My understanding was that TFS 2010 has an upgrade feature included in the wizard that should take care of most things for you. Thus far, I've only installed TFS 2008 from scratch and TFS 2010 from scratch-- I haven't yet tried that part of the wizard.
Another consideration is the database platform for your TFS 2008 instance. In our case, our 2008 is installed on MS SQL Server 2005, and TFS 2010 requires SQL Server 2008, so that's going to make our upgrade potentially a bit trickier.