TFS 2013 SharePoint Extensions cannot be installed on Windows 2012 R2 - tfs

Share point and TFS server (on Win 2012 R2) are installed on different systems. How do we configure extensions for SharePoint Products through TFS 2013 update 4? Every time I get an error:
SharePoint Foundation 2013 cannot be installed on Windows 8.1 or Windows Server 2012 R2

Firstly, you should install SharePoint Extension on the SharePoint server machine, not on TFS server machine.
Secondly, I think it worth for you to take a look at of this case: SharePoint Foundation 2013 cannot be installed on Windows 8.1 or Windows Server 2012 R2
So, you can try to install SharePoint Foundation 2013 with SP1 or TFS2013 Update 2 first, then run the TFS installer.

Related

Visual studio 2017 unable to connect to TFS 2008 URL

I'm unable to connect TFS 2008 URL from VS2017; Is there any patch or providers needs to be installed
Googled alot about msscci provider,
but there isn't anything specific for 2017!
I keep a blogpost with the most up-to-date information on which versions of Visual Studio connect to what and which things you need to have installed. TFS 2008 has been out of support for a while now (April 2018) and Visual Studio 2017 can't connect to it anymore as a result. Team Explorer 2010 is the last version that officially supports connecting to this old TFS version.
In order to work with TFS 2008, you need Team Explorer 2010 or lower installed and use that for your interactions with TFS 2008. This does mean that you won't have any working Team Explorer or Source control integration in the Solution Explorer.
It's highly recommended to upgrade TFS 2008 to TFS 2018 or the soon to be released Azure DevOps Server 2019. Or, take away the maintenance burden of having to run your own servers, by migrating to Azure DevOps in the cloud. The process to migrate does require an intermediate upgrade to TFS 2018 though, so I'd start with that regardless.
What to download and install for:
Team Explorer 2010
Correct TE 2010 download location
Team Explorer 2008

Stand-alone MS VSTS TFS Access for Windows Server 2008 (NOT R2)?

Yes, I know server 2008 is ridiculously old; but it is a client machine we cannot do anything about. Got that out of the way.
The client has an application which we maintain, and the source code lives on that machine, which is also the only machine around with VB6 on it (did I mention this project is old?).
I would like to find a client for the VisualStudio.com TFS services which can run on Server 2008 (not R2). Is there such a beast?
I've tried
Visual Studio Code
Visual Studio Community
TFS 2010 Power Tools
2017 Team Explorer standalone
Sadly, none of them are compatible.
Visual Studio is a kind of client of VSTS. But to be compatible server 2008 system. You could only use versions under Visual Studio 2008/Team Explorer 2008 for source control.
When you install Visual Studio 2008/Team Explorer 2008 successfully, you could also use TF Command to do version control for your project.

How to connect AX 2009 with Visual Studio Online (Visual Studio Team Services)

I'm trying to connect my AX 2009 installation to VSO (recently renamed to VSTS).
After browsing some forum entries I know that I have to install the following:
Install Visual Studio 2008 (not the Express Edition)
Install Team Explorer 2008
Install Visual Studio 2008 SP1 (This will upgrade both VS2008 and Team Explorer 2008 to SP1)
Install VSTS 2008 Forward Compatibility Update
The installation order is important because the SP1 will update VS and Team Explorer, so I followed that order.
Then I created a project in Visual Studio Online.
Now I want to connect my AX 2009 with the repository in VSO. The VSO is hosting a TFS, so this should work.
As far as I could find out to configure the TFS settings you need to set the Version Control Parameters and the System Settings. I did both as shown in the following screenshots:
When I'm setting the Version Control Paramters the Internet Explorer opened and I needed to authenticate with my User and Password against VSO (so this seems fine to me).
The final step now would be to Create the Repository (Tools -> Developer Tools -> Version Control -> Create Repository. But when I try to do this I get the following error-log: Team Server connection error. [Microsoft][ODBC SQL Server Driver][DBNETLIB]SQL Server does not exist or access denied.
The settings in 7 could be wrong - I'm not really sure what values are to set there.
Any help is appreciated.
The plugin is trying to access a SQL Server database. As VSTS is hosted on Azure and uses multi-tenanting there is no access to SQL server on that URL.
I am pretty sure that this is not ever going to work. VSTS is NOT just hosted TFS and even if it were, Visual Studio 2008 is no longer supported as a client for either TFS or VSTS.
Install the following components:
Visual Studio 2010 with SP1 (can be installed side by side with, or as a replacement for VS2008).
Team Foundation Server 2010 SP1 Object Model
KB 2662296
KB 2736182
There's additional discussion around this on the Dynamics Community AX Forum.

Move from TFS 2012 Express to full version on different PC

I am running a TFS server for little home projects... 2012 express on a Windows 7 SP2 machine. I am now upgrading to a Windows Server 2012 machine, and full version of TFS 2012. Is there a way to backup my current TFS setup, and restore it to my new PC?
This guide should show you how to upgrade from express to a full version: http://msdn.microsoft.com/en-us/library/vstudio/jj620928.aspx
This describes specifics for moving to new hardware: http://msdn.microsoft.com/en-us/library/vstudio/jj620930.aspx

Connecting Visual Studio 2005 to Team Foundation Server 2008

As of now we are using vs2005. We are newly setting up TFS 2008. How do I connect TFS 2008 client to vs 2005 without upgrading it to vs2008 in my system? When I installed TFS 2008 client the options are appearing in VS2008 but not in vs2005.
We have been using VS2005 with the Team Explorer client for 2005, talking to a TFS2008 server for a fewe months. When we upgraded from TFS2005 to 2008, we had no issues with client connectivity at all. If you are sticking with VS2005, then you should not need to install the 2008 client - just use the 2005 one.

Resources