I'm currently planning to upgrade our TFS 2008 server to TFS 2010 with the condition below:
1. upgrade everything except for the sharepoint
2. upgrade everything including sharepoint but sharepoint will be enabled only at later stage. will this stop us from using TFS for our development?
Thanks,
Chen
Sharepoint shouldn't be a requirement unless you have a strong need to have project portals. Everything else (workitems, source repository, etc. should work fine).
Related
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 5 years ago.
Improve this question
Since TFS 2018 does not support SharePoint integration, which databases should be migrated and what should be done with the SharePoint databases.
Update:
If you are upgrading to TFS 2018 from a previous version configured to integrate with SharePoint 2010 or 2013, you will need to disable the SharePoint integration after upgrade, or your TFS SharePoint sites will fail to load.
During installation, if SharePoint and TFS are on the same server, the installer will display the following warning message:
TFS 2018 and later versions no longer support integration with
SharePoint. If you have configured TFS integration with SharePoint,
then you will need to disconnect to the TFS Integration on each
SharePoint server, or your TFS SharePoint sites will not work.
After upgrading the TFS server, you must uninstall the prior version of the TFS from the SharePoint server. After uninstalling the TFS, the TFS SharePoint sites will fail to load. This is because they reference TFS artifacts that no longer exist.
The solution is to install the TFS Disconnector for SharePoint on the SharePoint 2013 server. The TFS Disconnector for SharePoint installs all the required references for TFS sites to display properly, while disabling TFS-SharePoint integration.
After the upgrade, your TFS SharePoint sites will display, but all integration functionality is disabled. The following image shows what the site will look like after you upgrade and disable SharePoint integration.
For more information, read Disable SharePoint integration after TFS 2018 upgrade.
Also take a look at Future plans for TFS and VSTS SharePoint integration
There are a number of changes coming to Team Foundation Server requirements in TFS 2018. Details on requirements across versions of TFS can be found in requirements and compatibility. Before you upgrade to TFS 2018, take a look at below note:
Operating systems
TFS 2018 will not support Windows Server 2008 R2, Windows 7, Windows
8.1, or Windows 10 Home edition. We have never recommended installing TFS on client OSes except for evaluation purposes or personal use. We
will continue to support Windows 10 Professional and Enterprise
editions.
SQL Server
TFS 2018 will no longer support SQL 2014, but will continue to support SQL 2016 and will add support for SQL 2017. We typically
strive to support at least one "overlapping" version of SQL between
major releases of TFS in order to make it easier to upgrade TFS
deployments incrementally.
SharePoint
TFS 2018 discontinues support for the TFS Extension for SharePoint.
For more information, go here:
https://go.microsoft.com/fwlink/?linkid=852977.
Build compatibility
TFS 2018 will no longer support the XAML build system. For more
information, go here:
https://blogs.msdn.microsoft.com/bharry/2017/05/30/evolving-tfsteam-services-build-automation-capabilities/.
If your TFS2015 installed on a not support system, you may have to first set up a new operating system.
Even though there is not a complete tutorial for TFS 2015 to TFS 2018 upgrade procedure by now. You could refer this article aims to expand on the Upgrade overview and give a step by step walk-through of the upgrade to TFS 2017. You just need to take care of some notes mentioned above.
The general process for upgrading an existing deployment of Team Foundation Server is to:
Prepare your environment. Such as upgrade your SQL sever
(required), operating system...
Expect the best, prepare for the worst. The single most important step you can take here is to ensure you have a complete and consistent set of database backups.
Do the upgrade!
Configure new features.
I don't think that you will find one complete guide in doing this, but a source of information is the Requirements and compatibility page.
There are different considerations depending on your configuration, e.g. do you use SharePoint, Reporting Services etc. One thing that you need to deal with, is that TFS 2015 and TFS 2018 does not support the same versions of SQL server, so you will need to upgrade SQL during the upgrade or move your collection(s) to a new server with the appropriate version of SQL (see here).
I would suggest to do a test migration of one or more collections and sort out the process before attempting it on your production server.
We have recently moved our TFS to be hosted # visualstudio.com.
Initially we selected Microsoft Visual Studio Scrum 2.2
We want to change this to MSF for agile development 6.2
Is there an easy way to do this.
Please note this is using the hosted TFS solution from Microsoft.
Has anyone tried to integrate Tibco Designer especially for BusinessWorks with Team Foundation Server 2010?
At the moment, our Tibco designer is using VSS as its source safe control.
We are planning to migrate the VSS to TFS 2010 but I could not find a solution to integrate Tibco Designer with the TFS 2010.
I have no familiarity with the product directly, but since it is currently able to integrate with SourceSafe, perhaps the TFS 2010 MSSCCI provider might help?
You would install it on your client machine(s) so that application would be able to talk to TFS 2010 (and 2005/2008 with that version, it seems). I have used the provider for getting Visual Studio 2003 to TFS 2010, which does not have native TFS support.
Visual Studio Gallery Page for TFS 2010 MSSCCI Provider
Yes we have integrated Designer with TFS in a retail project, but it does not leverage full strengths of a source control system. There are no auto builds, trunking. Just basic check-in check-out. For Designer SVN is a recommended source control system.
We're looking to upgrade to Delphi 2010 and have Team Foundation Server as our source Control.
Is there a plug in for TFS that allows clients to talk to it via SVN?
I noticed that CodePlex, Microsoft's open source web service, supports TFS and SVN so am hoping that there is a SVN plug in for TFS.
Ian
have a look at the SvnBridge project, which is I believe what Codeplex are using
Delphi used to support MSSCCI for version control plugins. If it still does you would be able to use the TFS MSSCCI provider and get TFS integration without using SvnBridge.
Can I use TFS Client 2010 with TFS server 2008?
Or it is not recommended ...?
We seem to be doing OK with this exact setup. All of the team queries, documents, reports, builds and source control integration seem to be working just fine. Admittedly, we've only been in the 2010 environment (against TFS2008) for about a week now.
That said, I imagine if we were going to run into issues, we would have by now.