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.
Related
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.
When I'm logged in to tfs build server using local account and execute following powershell command:
Add-PSSnapin Microsoft.TeamFoundation.PowerShell
it loads the tfs cmdlets correctly. However, when I trigger a build on tfs server that invokes the script, it fails with message:
'Microsoft.TeamFoundation.PowerShell' is not installed on this computer.
The build agent runs under service account. What should I do?
EDIT:
I had to edit the reqistry entry from the first link in #Alexis Coles' answer to make it work with version 2015 of TFS PowerTools:
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\PowerShell\1\PowerShellSnapIns\Microsoft.TeamFoundation.PowerShell]
"PowerShellVersion"="4.0"
"Vendor"="Microsoft Corporation"
"Description"="This is a PowerShell snap-in that includes the Team Foundation Server cmdlets."
"VendorIndirect"="Microsoft.TeamFoundation.PowerShell,Microsoft"
"DescriptionIndirect"="Microsoft.TeamFoundation.PowerShell,This is a PowerShell snap-in that includes the Team Foundation Server cmdlets."
"Version"="14.0.0.0"
"ApplicationBase"="C:\\Program Files (x86)\\Microsoft Team Foundation Server 2015 Power Tools"
"AssemblyName"="Microsoft.TeamFoundation.PowerTools.PowerShell, Version=14.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a"
"ModuleName"="C:\\Program Files (x86)\\Microsoft Team Foundation Server 2015 Power Tools\\Microsoft.TeamFoundation.PowerTools.PowerShell.dll"
"CustomPSSnapInType"="Microsoft.TeamFoundation.PowerTools.PowerShell.TFPSSnapIn"
[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\PowerShell\1\PowerShellSnapIns\Microsoft.TeamFoundation.PowerShell]
"PowerShellVersion"="4.0"
"Vendor"="Microsoft Corporation"
"Description"="This is a PowerShell snap-in that includes the Team Foundation Server cmdlets."
"VendorIndirect"="Microsoft.TeamFoundation.PowerShell,Microsoft"
"DescriptionIndirect"="Microsoft.TeamFoundation.PowerShell,This is a PowerShell snap-in that includes the Team Foundation Server cmdlets."
"Version"="14.0.0.0"
"ApplicationBase"="C:\\Program Files (x86)\\Microsoft Team Foundation Server 2015 Power Tools"
"AssemblyName"="Microsoft.TeamFoundation.PowerTools.PowerShell, Version=14.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a"
"ModuleName"="C:\\Program Files (x86)\\Microsoft Team Foundation Server 2015 Power Tools\\Microsoft.TeamFoundation.PowerTools.PowerShell.dll"
"CustomPSSnapInType"="Microsoft.TeamFoundation.PowerTools.PowerShell.TFPSSnapIn"
Double check AssemblyName, ApplicationBase, ModuleName and Version entries. Script above works with Microsoft Team Foundation Server 2015 Power Tools
I had this issue and to solve I notice that by default the cmdlets are not added during the PowerTools installation. You need to run a full install to make it work.
I posted here some pictures:
https://fabiostawinski.wordpress.com/2016/07/11/the-windows-powershell-snap-in-microsoft-teamfoundation-powershell-is-not-installed-on-this-computer/
I am going to have a quick punt here and say it is probably something to do with 32-bit vs 64-bit powershell. If I run Add-PSSnapinicrosoft.TeamFoundation.PowerShell from normal 64-bit powershell fine. But if I run it from C:\Windows\SysWOW64\WindowsPowerShell\v1.0\powershell_ise.exe I get the above exception. I am going to go ahead and say that the build server is a 32-bit application and there for starting a 32-bit runtime.
Not really sure what the fix is exactly but maybe the following will point you in the right direction.
PowerShell (2.0, 32-bit) can't load TFS 2010 snap-in... except when it can
https://social.msdn.microsoft.com/Forums/en-US/a116799a-0476-4c42-aa3e-45d8ba23739e/tfs-power-tools-2008-powershell-snapin-wont-run-in-on-64bit-in-windows-2008-r2?forum=tfspowertools
For me it was another issue because I was trying to use Power Tools with only Visual Studio 2017 Pro installed.
For Visual Studio 2017 they didn't released Microsoft Team Foundation Server 2017 Power Tools. They are saying that the previous version it should work with any higher version of Visual Studio that has TFS.
The problem is that if you have only Visual Studio 2017 installed you will not be able to install Microsoft Team Foundation Server 2015 Power Tools for example, because having Visual Studio 2015 (any version) installed is a requirement for installing Microsoft Team Foundation Server 2015 Power Tools.
In other words I had to install Visual Sudio 2015 then install Microsoft Team Foundation Server 2015 Power Tools and then Add-PSSnapin Microsoft.TeamFoundation.PowerShell worked.
Please refer also to this:
https://developercommunity.visualstudio.com/content/problem/103642/team-foundation-server-2015-power-tools-install-is.html
Hopefully this would help somebody.
In the video here the Entity Data Model Wizard includes options "EF Designer from database" and "Code First from database"
I do not get these options appearing in the wizard when I add a new data item and select ADO.Net entity data model
I am using VS2013 and have installed EF6.1 using Nuget. How do I install the new wizard options?
in VS Help About reports
Microsoft Visual Studio Professional 2013
Version 12.0.30110.00 Update 1
Microsoft .NET Framework
Version 4.5.50938
Installed Version: Professional
LightSwitch for Visual Studio 2013 06177-004-0447006-02694
Microsoft LightSwitch for Visual Studio 2013
Microsoft Office Developer Tools for Visual Studio 2013 ENU 06177-004-0447006-02694
Microsoft Office Developer Tools for Visual Studio 2013 ENU
Team Explorer for Visual Studio 2013 06177-004-0447006-02694
Microsoft Team Explorer for Visual Studio 2013
Visual Basic 2013 06177-004-0447006-02694
Microsoft Visual Basic 2013
Visual C# 2013 06177-004-0447006-02694
Microsoft Visual C# 2013
Visual C++ 2013 06177-004-0447006-02694
Microsoft Visual C++ 2013
Visual F# 2013 06177-004-0447006-02694
Microsoft Visual F# 2013
Visual Studio 2013 Code Analysis Spell Checker 06177-004-0447006-02694
Microsoft® Visual Studio® 2013 Code Analysis Spell Checker
Portions of International CorrectSpell™ spelling correction system © 1993 by Lernout & Hauspie Speech Products N.V. All rights reserved.
The American Heritage® Dictionary of the English Language, Third Edition Copyright © 1992 Houghton Mifflin Company. Electronic version licensed from Lernout & Hauspie Speech Products N.V. All rights reserved.
ASP.NET Web Frameworks and Tools 2012.2 4.1.21001.0
For additional information, visit http://go.microsoft.com/fwlink/?LinkID=309563
ASP.NET Web Frameworks and Tools 2013 5.0.11213.0
For additional information, visit http://www.asp.net/
BusinessObjectEditor 1.0
Information about my package
Common Azure Tools 1.0
Provides common services for use by Azure Mobile Services and Windows Azure Tools.
CreateLayoutWizard 1.0
Create layout wizard.
DevExpress.DeploymentTool 1.0
A useful tool for deploying DevExpress assemblies.
DevExpress.ExpressApp.Design.DesignDynamicPackage 1.0
DevExpress VSIX Package
DevExpress.ExpressApp.DesignPackage 1.0
DevExpress VSIX Package
DevExtreme.Design 14.1.7
DevExtreme Visual Studio integration package
JetBrains ReSharper 8.2 Full Edition build 8.2.0.2160 on 2014-03-20T08:53:08
JetBrains ReSharper 8.2 package for Microsoft Visual Studio. For more information about ReSharper, visit http://www.jetbrains.com/resharper/. Copyright © 2003–2014 JetBrains, Inc.
Microsoft Web Developer Tools 2013 2.0.40926.0
Microsoft Web Developer Tools contains the following components:
Support for creating and opening ASP.NET web projects
Browser Link: A communication channel between Visual Studio and browsers
Editor extensions for HTML, CSS, and JavaScript
Page Inspector: Inspection tool for ASP.NET web projects
Scaffolding: A framework for building and running code generators
Server Explorer extensions for Windows Azure Web Sites
Web publishing: Extensions for publishing ASP.NET web projects to hosting providers, on-premises servers, or Windows Azure
NuGet Package Manager 2.8.50126.477
NuGet Package Manager in Visual Studio. For more information about NuGet, visit http://docs.nuget.org/.
PreEmptive Analytics Visualizer 1.2
Microsoft Visual Studio extension to visualize aggregated summaries from the PreEmptive Analytics product.
SQL Server Data Tools 12.0.30919.1
Microsoft SQL Server Data Tools
TechTalk SpecFlow 1.9.3
TechTalk SpecFlow - Binding business requirements to .NET code, http://www.specflow.org
Copyright © 2009–2013 TechTalk
Windows Azure Mobile Services Tools 1.0
Windows Azure Mobile Services Tools
Workflow Manager Tools 1.0 1.0
This package contains the necessary Visual Studio integration components for Workflow Manager.
XtraReports package 1.0
XtraReports package
Do you have the latest quarterly update for Visual Studio? Look for the little flag in the upper right corner which will tell you if you need to update any components or VS2013.
You are running update 1. Update 3 is the latest stable release which can be downloaded:
Microsoft Visual Studio 2013 Update 3
Alternate and Quick Solution ->
For me, it worked there by downloading & installing EFTools6.1.3ForVS2013.msi (19.6 MB) version from Microsoft Download page for Entity Framework 6 Tools for Visual Studio 2012 & 2013
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."