How can one migrate from Visual Studio Online to an on-premises instance of TFS (version 2017)?
Ideally I'd like to migrate all code, project management data, etc.
Thank you for your time
There's no way to do this without the use of third-party tools, all of which will result in some amount of data loss.
There is currently no way to move from VS Team Services to Team
Foundation Server or to export a project or project collection in such
a way that it can be attached to a TFS server.
Depending on what features of VS Team Services you're using it may be
possible to migrate some of the data to a new target environment with
relative ease. And depending on what you're willing to lose you may be
able to migrate some other bits easily as well.
There are 3rd party tools that offer migration to and from VS Team
Services, though these can be pretty expensive.
Refer to this thread for details: Move from VS Team Service to an on-premises TFS
Related
I do have two visual studio online accounts:
mypersonalaccount.visualstudio.com (free basic) and
mycompanyaccount.visualstudio.com (paid)
I started a small project into my personal one a few years ago. Now this project grows up and we create a little company.
I would like to change this project from my personal account to the my company account. in order to take advantage of the paid features.
How can I migrate a project from one account to another?
I would like to change the ownership for all data, no just the code repository but all tasks and sprints data too.
There is no such tool provided by Microsoft. Microsoft supports the migration from Team Foundation Server on premise to Visual Studio Team Services.
What I would suggest is to either use alternative tools like the vsts-sync-migration, or write your own PowerShell scripts leveraging the VSTS REST APIs to move the data you need.
Got 5 different TFS, is there a way to search in all TFS's? Visual studio plugin?
Right now I've downloaded all the source code to my local machine and turned on indexing on serveral filetypes (properties and inside files)..
If anyone has the same problem, how do you solve this kind of problem?
Never heard this kind of tools or plugin.
In a sense, there are different Application Lifecycle Management system. They have different servers, SQL servers, users, permission settings and so on. Searching between them, how could this be possible to achieve. Unless, you choose to migrate different projects to one instance of TFS.
OpsHub Integration Manager supports bi-directional synchronization between a wide variety of systems including Team Foundation Server and Visual Studio Online. It can be used for bi-directional sync between TFS and VSO. For more information please reach out to OpsHub at http://www.opshub.com/main/index.php/company/contactus
We are trying to work on a solution to synchronize two TFS 2013
servers.
We have two TFS 2013 servers, one in the development environment
(let's say TFS 2013 Development) and the other in the production
environment (TFS 2013 Production).
We need to be able to:
Synchronize pieces of code from TFS 2013 Development to TFS 2013
Production on an as needed basis.
Synchronize the TFS tasks and work
items between TFS 2013 Development and TFS 2013 Production. This
should happen on an immediate basis and should be bi-directional. That
is, when any changes are made to the work items/tasks in either TFS
2013 Development or TFS 2013 Production it should immediately be
reflected on the other TFS server respectively.
We have started
looking into the above and tried using the TFS integration platform
for synchronizing code between the TFS 2013 development and TFS 2013
Production servers.
Hence we basically have three questions
Is TFS 2013 to TFS 2013 code/work item synchronization supported by the TFS integration platform tool?
How can we go about doing the Synchronization for the code
repositories and work items as described above for TFS 2013 to TFS
2013?
Is synchronization a new direct feature of TFS 2013, and can this
be done without any third party tools?
To start with, I don't understand the setup of your systems. TFS generally lives in 1 instance and 1 only. TFS is a production environment for the development team. It doesn't make sense to have two TFS systems and have them synchronize to make this separation.
If you need to create secure snapshots of your sources, you can create branches and secure these. If you need to promote the results, run a build and use the published build artifacts to install to the production environment.
Having your teams work on two different TFS environments at the same time is a very strange requirement.
To just answer your questions:
Now to answer your questions:
TFS Integration Tools
It's a feature of the tool, and as long as you use the TFS Integration Tools (the version available from the Visual Studio gallery), Microsoft provides paid support. The TFS Integration Platform doesn't come with the same level of support. The TFS Integration Tools do not synchronize all data between environments, work item Tags, Test Results, Check-in notes, Labels, Permissions, Workspaces, Pending Changes, Shelvesets, File encodings, Subscriptions, Test Cases, Check-in policies, Reports, Team Portal / SharePoint, Process Templates, Work item queries, Builds, Warehouse data are not supported.
setting up You'd setup two syncs, one bi-directional sync for work one one-directional for sources and pray. There are so many things that can go wrong in this situation, as the sync is not transactional across environments and certain actions can happen synchronously on both environments that will put you in a stuck state. Generally when syncing between two systems you'd make one system master for a specific piece of data and you son't touch them on the other environment. This scenario is a nightmare waiting to haunt you until you turn it off. For the source sync, you might opt for a manual checkout/checkin process instead.
Out of the box? No, this is not a supported scenario in TFS out of the box. There is the Integration tools (which you've already found) and there are a few 3rd party commercial tools like OpsHub and TaskTop.
TFS Integration Platform (March 2012 Release) supports only TFS2012
You can write your own synchronization tool using TFS API.
No. TFS2013 doesn't have this feature.
We have some unusual situation and need to migrate from TFS2010 to TFS2008. Does anybody know is it possible to make ?
If you don't need full fidelity - that is, you don't need to transfer shelvesets over, you don't mind rebuilding reports, etc - then you may be able to synchronize your TFS2010 server to a TFS2008 server using the Team Foundation Server Integration Tools.
We use these internally at Microsoft to mirror between various servers with regularity, and with good success.
Almost all of our projects involve a web application or winforms application and a data access layer (class library) and stored procedures/database scripts.
We are looking for a good way to organize the solutions, and found a few ways:
1)We could have a sql server management studio solution for all the db related things, then have a visual studio solution for the application and data access layer projects.
2)We could do it all in visual studio with 3 projects, a sql server project, a web app/winforms app project, and a data access layer project.
3)We could do it all in visual studio with 2 projects, a web app/winforms app project and a data access layer project, and just put the sql scripts in a directory in the data access layer project.
I'm sure there's other ways, but I'm just curious to see how others go about doing it.
I have done this successfully using Visual Studio Team System Database Edition - multiple types dot net projects with a database project in a single solution.
Keep in mind that deploying a database project takes much longer because you usually need test data and most inserts thereto are RBAR insert statements. We used to turn off deploying the database project until absolutely necessary (usually once or twice a week).
Of course, all of this was in TFS for source code control
SQL Server Management Studio solution
allow use GUI designer for creating and editing some objects.
Visual Studio Projects
allows use TFS as version control and more integrate work of all developers working with a database;
better implements IntelliSence
I use Management Studio and some batch files to export/import/store the sql in the solution (under source control too).
So each time there's a change in the db it's exported to the solution and a custom tool is run to update the ORM proxy classes.