This tool looks promising when I went through the available information on website. But when I downloaded free version and when I am trying to install in my local I came across the following error.
OPS-008: OpsHub Visual Studio Migration Utility requires Team Foundation Server 2012 Update 1 Object Model or above.
Do I need to install this software on the server ? No where I could find instructions for installing this software.
Can I get this explained please, we are planning to migrate our project to VSTS.
If you want to migrate from TFS on premise to VSTS, I would suggest you to evaluate which of the three options listed by Microsoft documentation suite your need.
The easier way would be to chose option 2, especially if you already have TFS2015update3 or TFS 2017, as you need to upgrade your TFS collection to one of those version anyway before migrating (and you save the upgrade hassle).
If you want to use OpsHub tool, then you need to install the standalone TFS Object Model for TFS 2012 update 4 where you run the OpsHub tool, not on any of the TFS servers.
In order to run OVSMU, you will have to install TFS Object Model 2012 on the machine where you are installing the tool. This is a pre-requisite and be rest assured this version of OM will not conflict with any other (newer) version of Object Model already existing (which comes bundled with Visual Studio installer) on that machine.
Related
I've read numerous articles and posts here about getting Entity Framework to work with DB2 but all of them reference prior versions of Visual Studio. When I repeat the steps outlined (too many to remember at this point), I still do not have DB2 in the data providers list.
Has anyone gotten this to work in VS17 and, if so, can you walk me through what you did?
For registering IBM Database Add-Ins for Visual Studio 17, Visual Studio 2015 or earlier supported versions needs to be installed on the machine.
Steps:
Download and install IBM Data Server Driver Package
Download and install IBM Database Add-Ins for Visual Studio.
After successful installation of IBM Database Add-Ins, choose Start -> IBM Database Add-Ins for Visual Studio ->Register IBM Database Add-Ins.
This link has listed the steps needed for the add-in installation
https://www.ibm.com/developerworks/community/blogs/96960515-2ea1-4391-8170-b0515d08e4da/entry/VSAIFORVS2017?lang=en
Note: Make sure to download same version and fix pack of DS Driver and VS IBM Database Add-In. I downloaded v11.1.3fp3 version for both installations and it's working for me.
I want to connect sqlite using EF6 in VS2017.
I installed "System.Data.SQLite" nuget package.
I also installed "sqlite-netFx46-setup-bundle-x86-2015-1.0.104.0.exe" from http://system.data.sqlite.org, but I cannot see the sqlite provider when adding ADO.NET data entity.
Am I missing something? or the above package not supporting VS2017 (it said it is for VS2015)
There is no DDEX provider package for VS 2017 (yet). https://system.data.sqlite.org/index.html/tktview?name=8292431f51
Basically you need to wait for: sqlite-netFx46-setup-bundle-x86-2017-1.0.1xx.0.exe
"Official" update:
The current estimate is that support for Visual Studio 2017 will
be included in the 1.0.106.0 release, which should be released at
some point in the mid-June timeframe.
mistachkin added on 2017-05-28 20:41:40: At this point, it seems unlikely that I'll be able to add VS 2017 support for the design-time components (e.g. table designer, entity wizard, etc).
UPDATE: I have created a DDEX provider that enables SQLite support (for EF6 only) in Visual Studio 2017, see the how-to guide here: https://github.com/ErikEJ/SqlCeToolbox/wiki/EF6-workflow-with-SQLite-DDEX-provider
The issue was solved after installing SQLite/SQL Server Compact Toolbox.
Please try. https://marketplace.visualstudio.com/items?itemName=ErikEJ.SQLServerCompactSQLiteToolbox
The VS 2017 installer is really a pain in the b***.. Installing packages via an automated deployment works, but detecting installation state and such is near to impossible..
Seems like microsoft devs finally got sick of msi packages and implemented their own installer / package manager for VS2017, as other teams did for Office 365 and such..
According to the url provided by the sqlite-netFX46-bundle-win32-2015-1.0.108.0 intaller log : https://system.data.sqlite.org/index.html/info/8292431f51119807241632b092774e60189018d9 Visual Studio 2017 support isn't available yet
I tryied many things without any result, the worst is that I installed also a VS 2015 but cannot install because of the VS 2017 installation on my computer.
I am looking to migrate from TFS 2012 on-premises to Visual Studio Online using the OpsHub Visual Studio Online Migration Utility. I have run into an issue that I can't seem to find a resolution for. To eliminate any customization, I have created a brand new team project in TFS 2012 using the process template SCRUM 2.0. I did nothing else after creating that new project. The goal was to run the migration utility on this new project to see if I can get it to work. During the migration, it fails with the error "Template Customization or Template Mismatch Error". Since I know for sure we never modified the SCRUM 2.0 process template that I used to create this new project, I assume the error is more with the fact that TFS 2012 SCRUM 2.0 template is different that Visual Studio Online. Using TFS Team Project manager utility I can see they are quite different.
So the question is, does OpsHub not support migration from TFS 2012 to Visual Studio Online when no customization to process template was made? It does not look like it does unless I am missing something. Can anyone help me determine what I need to do to make this migration a success.
Thanks,
The OpsHub tool supports migration only when the local template matches the target template. You will need to upgrade your Scrum team project to the latest scrum template to proceed.
You can also use the TFS Integration Tools to migrate with a mapping between the two templates. That might work better for you, but the TFSIP is significantly more complicated than the free OpsHub took. But that complexity brings features.
Tool is throwing error because the fields listed in error have display name do not match fields in VSO. In upgraded process template version 2.2 and other above version they have space included in display name such as Related Link Count. To overcome this error you can upgrade the process template version to 2.2 or use witadmin.exe tool to change the field display name. For more details visit here
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 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.