Does anyone know what happened to the Powershell power tools for TFS 2017?
I have existing scripts for TFS and would like to keep using them.
I tried installed the 2015 tools but they will not install because it requires VS 2015 and I am using 2017.
To my knowledge there are no Power Tools for Team Foundation Server 2017 (see https://www.visualstudio.com/en-us/news/releasenotes/tfs2017-relnotes).
That said you can leverage #igor-abade Powershell CmdLets (https://github.com/igoravl/tfscmdlets) which offer a good deal of features.
Related
One of our client wants to move from TFS 2013 to TFS 2018. We don't have much information about the current TFS setup at client's end.
Can anyone please guide with what questions we need to ask to client to get the information regarding the current TFS system setup before we start with upgrade process.
Also share if there is any process document regarding upgrading the TFS 2013 to TFS 2018.
Thanks in advance.
You need to confirm the real requirements first, need to upgrade or migrate?
Check if the current device, OS and software match the Requirements and compatibility for the upgrade/migration :
Client operating systems:
TFS 2018 Windows 10 (Professional,Enterprise) Version 1607 or greater
TFS 2013 Windows 8.1 (Basic, Professional, Enterprise) Windows 7
(minimum SP1) (Home Premium, Professional, Enterprise, Ultimate)
SQL Server:
TFS 2013 Update 4 - SQL Server 2014 or SQL Server 2012 (minimum SP1)
TFS 2018 - SQL Server 2017 or SQL Server 2016 (minimum SP1)
Upgrade is a full data transfer. You will have all data in the previous TFS.
As TFS 2018 only supports SQL Server 2017 and SQL Server 2016 (minimum SP1), upgrade SQL Server is necessary.
You need to go through article Upgrade your deployment to the latest version of TFS before doing upgrade. And follow the steps in article Upgrade scenario walkthrough for Team Foundation Server to upgrade your TFS. Summarize the steps here:
Prepare your environment. The first step is to check the system
requirements for TFS 2018. Upgrade SQL Server is necessary for your
scenario. Including SQL Server, you also need to check other system
requirements and prepare the environment.
Expect the best, prepare for the worst. You must have a complete and
consistent set of database backups in case something goes wrong.
Do the upgrade. Once the preparation is done, you'll need to install
the new version of TFS to get new binaries, and then run through the
upgrade wizard to upgrade your databases.
Configure new features. Depending on what version you upgraded from,
you may need to configure each team project to gain access to some
of the new features made available.
Below threads for your reference:
https://blogs.msdn.microsoft.com/rob/2016/12/22/upgrading-from-tfs-2013-to-tfs-2017/
TFS 2012 to TFS 2018 Migration/Upgrade Path
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.
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.
when running windows 8.1 I had the windows explorer extension that allowed TFS 2013 integration.
After an upgrade to Windows 10 that has "made off" as the police would like to say.
Has anyone got this working and if they have what did they do?
Beginning with Visual Studio 2017, a new extension called Microsoft Team Foundation Version Control Windows Shell Extension has been published to the Visual Studio Marketplace.
The description says:
This release requires a computer with Visual Studio 2017 and all of the Visual Studio system requirements. It supports all TFS Server versions that are supported by Visual Studio 2017:
Team Foundation Server 2018
Team Foundation Server 2017
Team Foundation Server 2015
Team Foundation Server 2013
Team Foundation Server 2012
Team Foundation Server 2010 SP1
Visual Studio Team Services
I have finally got to the bottom of this. It turns out that you dont match the power tools to teh TFS version (even though they are TFS power tools), you match them to the Visual Studio version regardless of the TFS version.
So in my case I have visual studio 2015 and TFS 2013. I need to install the power tools for TFS 2015.
Thanks for your help everyone
Dave is correct that, you need to install TFS 2013 Power Tool to use Windows Shell Extension.
Then you can get the extension in a local folder which is in a TFVC mapped workspace folder.
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.