I have both Visual Studio 2008 and 2010 connecting to TFS 2008.
In Visual studio 2008 i can see the if some particular person has checked out any file by the option
Find in source control > Status
But when I am trying to see same thing via 2010 I can't find it.
When I try to install the Visual Studio 2010 Power Tools for Team foundation Server (Dec '11), I get the following error message:
TFS Power Tools
Setup detected that a previous version of this product installed for the following users. These per-user ("Just Me") installations must be removed before this version of the Microsoft Team Foundation Server 2008 Power Tools can be installed on the machine ("Everyone").
Close
This option in available through the Visual Studio 2010 Power tools for Team Foundation Server. You can install multiple versions of the Power Tools side-by-side, but you can only have one version of the Windows Explorer extensions installed. I usually opt for the latest version for that feature.
Uninstall the older version of the power tools and then install them (oldest to newest). For each older version deselect the "Windows Explorer Integration" and the "Powershell cmd-lets", I tend to only install the latest version of those.
You can find the older versions here:
2005: Microsoft Visual Studio 2005 Team Foundation Server Power Tools - September 2007 release
2008: Visual Studio Team System 2008 Team Foundation Server Power Tools - October 2008 Release
2010: Team Foundation Server Power Tools December 2011
2012: Microsoft Visual Studio Team Foundation Server 2012 Power Tools
2013: Microsoft Visual Studio Team Foundation Server 2013 Power Tools
When installing make sure you always select to install for "All Users" that way you should be able to install all of these side-by-side as long as the corresponding version of Team Explorer is installed as well.
If you're connecting to TFS 2008, then you only need the TFS Best Practice Analyzer from the 2008 power tools and you should use the Visual Studio 2008 Developer Command Prompt for commands that do Team Project Creation or interact with Sharepoint/ReportServer. This is exactly the same as when you're editing Work Item Definitions using witadmin, you can't edit the 2008 work items definitions with the 2010 version of widadmin.
From experience, the following commands/features are server version specific:
Tfpt addprojectreports
Tfpt addprojectportal
Tfpt createteamproject
Work Item Editor
Best Practice Analyzer
And these should work with any TFS version as long as the corresponding version of Team Explorer supports said TFS version.
Explorer Integration
Check-in policy pack
Source Control Explorer extensions
Team explorer extensions
Work Item templates
Powershell commandlets
Other tfpt commands
A complete overview of the tools that will/will not work depending on your TFS and Visual Studio version can be found on my blog.
You should install the Windows Explorer extensions and Powershell cmd-lets from the highest version of the Power Tools you intend to install. The latest version has seen the most development and will have fewer bugs.
The 2010 tools won't break your TFS 2008 installation.
You may need to open and activate the Source Control Explorer to see this menu command. This is the case in VS 2015.
Related
Is it possible to open a SSIS solution using Microsoft's free tools (Visual Studio Team Explorer and SQL Server Data Tools) or does it require a full installation of Visual Studio?
I am trying to do so with just the free tools and am getting an error saying that "this versino of Visual Studio is unable to open the following projects" then another one saying the solution I have opened is under source control but not currently configured for integrated source control in visual studio.
We have other users who use the full version of Visual Studio 2017 and it works fine so I am wondering if this is just a limitation of the free products offered by Microsoft.
To edit SQL Server 2005 SSIS packages, you need Visual Studio 2005 and installation of Business Intelligence Designer Studio, BIDS. This required a license, developer edition was sufficient, to access the tooling.
SQL Server 2008 & SQL Server 2008 R2 would install into Visual Studio 2008. This too required a SQL Server license as the media only existed on the server media.
SQL Server 2012 would install into both Visual Studio 2010 and Visual Studio 2012. This was delivered in both physical media installations and downloadable tooling which was rebranded to SQL Server Data Tools- BI Edition, now just SQL Server Data Tools and the components were just licensed via click through agreement.
SQL Server 2014 installs into Visual Studio 2013 and was now only available through the download of SSDT.
SQL Server 2016 added a new twist into the mix. It installed into Visual Studio 2015 but it could now create/edit/target SQL Server 2012, 2014 and 2016 packages. This was huge as until this point, as a consultant I would have required 5 different versions of the "same" program on my machine. Now I'd only need 3.
SQL Server 2017 installs SSDT in both Visual Studio 2015 and Visual Studio 2017.
I assume SQL Server 2019 will similarly target VS 2017 and VS 109.
Across all of these versions, if you didn't have Visual Studio installed, the installer would install the Visual Studio shell on your machine so that the project templates would work.
Last I knew, neither Visual Studio Community Edition nor VS Code will work with the SSDT templates so be sure and open the correct product to work with SSIS projects (.dtproj)
The warning/error about "under source control but not currently configured" smells like something is awry with how you have the TFS hook installed but I can't comment on that.
Download and install SSDT 2017 for Visual Studio
You can verify the status of your SSDT installation for Visual Studio by going to the Help, About Microsoft Visual Studio menu and looking for "SQL Server Integration Services." With ... 2017? you can now do a piecemeal install and only pick SQL Server Data Tools (database projects) or SSAS/SSIS/SSRS. Previously, the SSDT-BI install was trio of SS_S and SSDT (no BI) was the database projects.
Previous answer on where SSDT-BI is
You have at lease two options:
Use Visual Studio Community Edition together with SSDT. Still, you have to check its License terms with your Legal department - it might be not legal to use Community Edition in Enterprise.
Use Visual Studio Isolated Shell together with SSDT. More instructions on how to install it. As far as I know, it is legal to use it for debugging.
The VS Isolated Shell is usually installed with SQL Server 2014/16.
I have some requirements that I need to use Visual Studio 2008 for a new SSIS package. But we are using visualstudio.com as our source control because we were allowed to use Visual Studio 2012 for our main project.
I tried following the instructions here http://www.visualstudio.com/en-us/get-started/connect-to-vs.aspx and here how to open Team Explorer in Visual Studio 2008 and no go.
Has anyone been able to connect to their TFS server at visualstudio.com from Visual Studio 2008? If so, how did you do it?
Officially VS 2008 is only supported against TFS 2013 (and Visual Studio Online) by using the MSSCCI. However, in practice it still works fine without MSSCCI, MS just no longer tests this particular scenario, so it's not guaranteed to continue working.
Make sure you have the appropriate updates installed, you need:
VSTS 2008 Team Explorer
VS 2008 SP1
TFS 2012 Compatibility GDR
Order of installation is very important. Refer to this article.
Moreover, if you are still having issues connecting to TFS after successfully installing above mentioned updates, consider clearing your IE browsing history (all checkboxes) and retry.
Per MSDN you can access version control on Visual Studio Online with Visual Studio 2008 using Team Explorer for Visual Studio Team System 2008 and MSSCCI 2013.
Is it possible to have the "team" plug-in for Excel (MS TFS 2012) without having to install Visual Studio 2012?
Thank you!
The Excel integration comes as part of Team Explorer for Visual Studio 2012. Installing it installs all the TFS integration bits on your machine (and allows you to install things like the Shell extension power tools). It does also install small Visual Studio shell but one that doesn't include any of the programming tools etc.
You only need a license to access your Team Foundation Server to install Team Explorer (i.e. a TFS CAL) - no additional Visual Studio license required.
You can try installing Visual Studio 2012 express web or some other version, if Team menu is not showing up yet in excel then try installing TFS 2012 Express also try installing Team Explorer for Microsoft Visual Studio 2012
I just installed VS2010 and I want to connect to TFS, But I don't have any team explorer options.
I searched for Team Explorer and I found this link that states that Team Explorer comes preinstalled in VS2010 Team Suit.
I downloaded VS2010 Pro and don't have team explorer and can't find it anywhere.
Any ideas? Tips?
Thanks
I think there's been a misunderstanding down MS naming conventions.
All versions of Visual Studio 2010 have the ability to conenct to TFS built in, there is no longer a separate install (what was previously called Team Explorer).
What the Ultimate edition gets with what is now called Team Explorer (codename Eaglestone) is a standalone rich client for accessing TFS.
If you downloaded VS2010 Pro...you didn't download a version that came with Team Explorer. You need to re-download VS2010 Team System. You can grab it from MSDN or download it from:
Visual Studio 2010 Team System Beta 1 Download
UPDATE
As of Beta 2, Microsoft renamed versions a little. TFS Connectivity is now included with 'Ultimate'.
It looks like Team Explorer is also available as a separate download. The VS 2010 Beta 2 version is here: http://www.microsoft.com/downloads/details.aspx?familyid=CA86215B-A824-44E7-B4C3-982C7ECEA46D&displaylang=en
The RTM version of Team Explorer is here: Microsoft Visual Studio Team Explorer 2010 - ISO
VS2010 Pro is a different release from VS2010 Team Suit and it doesn't contain anything that has to do with TFS. If you want to connect to TFS you need to get the VS2010 Team Suit release.
This has been the norm ever since VS2005.
You can download Visual Studio Team Explorer (or the command line tools) from the following:
Team Explorer 2013
Team Explorer 2012
Microsoft Visual Studio Team Explorer Everywhere 2010
Team Explorer 2008
Team Explorer 2005
I would like to upgrade my team from VS2005 to VS2008 without touching the version of Team Server which is 2005.
Is that possible?
And if so, how do I tell VS to recognize TFS?
Currently in my VS2008 options menu, I don't have any source control to choose from.
VS 2008 works fine with TFS 2005. There are a couple of exceptions in the Team Build area (which changed massively between 2005 and 2008) but otherwise you will be able to do everything you need to do from the Visual Studio 2008 client.
You need to ensure that you have the 2008 version of the Team Explorer installed to add TFS functionality into Visual Studio. The 2005 version only installs into Visual Studio 2005. To download the 2008 version see the following link
http://www.microsoft.com/downloads/details.aspx?familyid=0ed12659-3d41-4420-bbb0-a46e51bfca86
Note that if you have previously applied SP1 of Visual Studio 2008, then you will need to run it again once installing Team Explorer.
For what it is worth, I would encourage you to upgrade to TFS 2008 on the server side as soon as you can. TFS 2008 works fine with client connecting from Visual Studio 2005 machine but it has some significant performance improvements and the Team Build functionality is much improved.
Yes, you can... (We're doing that here too)
Tools -> Connect To Team Foundation Server
"Add..."
Enter IP / hostname
Yes, that works fine. If you install the Team Foundation Client from the TFS 2008 DVD on your VS machine, you can connect to both TFS 2005 and TFS 2008 servers. If you don't have access to a TFS 2008 DVD (note that the trial should be fine), installing the 2005 client on VS 2008 should also work, but I've never personally tried that.
Do you have the Team Foundation Client installed?
If you have the Team Version it should be residing in the TFC folder on your installation DVD. (I don't know why it isn't an option in the installer)
It is also possible to download the TFC from Microsoft (for free), there is an SP1 version on Microsoft Downloads.