I want to be able to connect to Team Server 2008 r2 to the Visual Studio.net 2012 that I installed on my workstation today. So far I am having problems.
I am making this change since I want to upgrade all my .net applications to using Visual Studio 2012.
Right now all my solution files have TFS attached to them since I loaded the solution files into TFS previously using Visual Studio 2010.
I have downloaded the plugin for Team server to install on my computer and I am advised that the plugin is installed on my computer. When I am in visual studio 2012 and I click on toos-->options-->source control and I get no options to select.
Thus can you tell me what you suggest that I do to solve my problem?
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 Team Foundation Server 2015 installed, and I'm trying to connect Visual Studio 2008 (Version 9.0.30729.4462 QFE) to the team project. I have installed VS 2008 Team Explorer (version 9.0.21022.8).
According to MS, this should be possible using MSSCCI Provider. However, I can't find the version that's compatible with TFS 2015.
Question: Where is the MSSCCI Provider for TFS 2015, or is there another way to connect VS 2008 to TFS 2015 ?
I have tried MSSCCI Provider for TFS 2013, and it failed because it didn't detect TFS 2013 (which makes sense since I have 2015 installed).
Did you install the vs2008 sp1 compatibility GDR? Or else please install it.. https://www.microsoft.com/en-us/download/details.aspx?id=29983
When passing the TFS URL in VS 2008 make sure that you are passing the tfs collection name as well, otherwise vs 2008 will throw error. For example, http://servername:8080/tfs/{collection1}
Edit: Please make sure that you install VS 2008 SP1 before you try steps 1 and 2.
In my case, I had no VS 2008 IDE was installed until yesterday.
Due to some conversion limitations in my company, I had to install the old Visual Studio 2008 to my office PC (Windows 10 Pro x64) and connect it to TFS 2015.
I hope this helps someone else like me:
First I've installed Visual Studio 2008.
And then VS 2008 SP1.
Lastly Visual Studio TeamExplorer 2008. (At least this should be the happy ending but I was wrong.)
Tried to install VS90SP1-KB974558-x86, but it failed. The package seeks for VS 2008 SP1. I think TeamExplorer 2008 overrides sth important for KB974558.
Installed Visual Studio 2008 SP1 again.
VS90SP1-KB974558-x86 installed successfully.
On the page "Connect to Team Foundation Server", add your TFS 2015 server by ignoring the port and protocol section, and write down your own like;
http://TFS_SERVER:PORT_NUMBER/tfs/TFS_COLLECTION_NAME
It fails everytime if I skip the collection name part.
Since I cant comment. I want to say that we have the same problem.
What works is installing the Visual Studio Team Explorer 2013 which includes a Visual Studio Shell 2013 and then we can install the MSSCCI Provider 2013. But thats just a workaround.
We also wonder where the MSSCCI Provider for 2015 is.
You can just use MSSCCI for TFS 2013 to connect to TFS2015 source control in VS2008.
Just as the MSDN article shown, in VS2008, Version Control is available via using MSSCCI Provider. So instead of connect to TFS in Team Explorer, you need to go to File -> Source Control -> Open from Source Control -> Connect to Team Foundation Server. I believe this blog is helpful to you (although it is written for TFS2013 with VS2005, it applies to TFS2015 with VS2008).
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.
I am trying to connect to my TFS 2010 RC server. When I try to connect I get a error message.
Here is a screen shot:
alt text http://xs.to/image-2537_4B8BEAA0.jpg
This is the path I am using to connect: http://tfs2010test:8080/tfs/DefaultCollection
I have Team Explorer 2008 SP 1 installed.
I have read this question: Visual Studio 2008: Can't connect to known good TFS 2010. That is how I got my path that I tried.
I can connect just fine using Visual Studio 2010.
What am I missing?
Have you installed the forward compatibility update from here? Further details can be found here.
Here was my solution to get Visual Studio 2008 Team System to connect to TFS2010: (Beware convoluted).
Install Visual Studio 2008 Team Explorer
Uninstall Office 2007 (because of an incompatibility between Visual Studio 2008 SP1 installer and Office 2007)
Run the Microsoft Install Clean Up utility to remove all references to Office 2007 that did not get removed when uninstalling)
Re-Install Visual Studio 2008 Service Pack 1
Install Visual Studio Team System 2008 Service Pack 1 Forward Compatibility Update for Team Foundation Server 2010
Reinstall Office 2007 or go to OpenOffice
Access TFS2010 repository...
When I have added TFS servers before, I could not add the port in the URL. Have you tried this without the port, and allow discovery?
A few things to try:
Have you tried connecting with Team Explorer 2010?
Have you tried creating a new project collection?
On your server, open the TFS admin tool and confirm that you have permissions to use that collection.
Be aware, some options are just not available in Team Explorer 2008.
Let me know if you need help with the security/groups on the server. It was very confusing to me when I first tried to work with it.
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.