How can I rename my Team Project that is hosted in Microsoft's Team Foundation Service? And how can I rename the area paths?
Unfortunately it is not possible in TFS 2005, 2008, 2010, 2012, or 2013. However the work to complete this has been done and it is now available on VSO and will ship in TFS 2015.
http://blogs.msdn.com/b/bharry/archive/2015/04/24/team-project-rename-available-on-vs-online.aspx
You can now rename team projects in Visual Studio Online and the upcoming TFS 2015 release: https://www.visualstudio.com/en-us/news/2015-apr-24-vso
The idea status changed to STARTED
Visual Studio Team (Product Team, Microsoft) responded On Feb 27, 2015:
Im am excited to announce that today we are planning to enable project
rename for TFS 2015. We don’t have an ETA yet for Visual Studio
Online.
If you want to see our progress, visit the Future Feature Development
page at http://www.visualstudio.com/en-us/news/release-archive-vso.
Ewald Hofman TFS Program Manager
Related
At work, I've been put into the role of TFS administrator, as the real TFS admin is leaving our organization in two weeks. We're currently using TFS 2015. I'm trying to upgrade us to TFS 2018, hopefully before the current admin leaves.
To that end, I've been reading various resources on TFS migration from TFS 2015 to TFS 2018. One resource I came across is this one Migration from TFS 2015 to 2018. This document spoke about integration between TFS 2018 and SharePoint. I had thought that integration died, after TFS 2015. Specifically, up to TFS 2015, TFS had what they called "TFS Project rooms". Sort of like a simple bulletin board type system. But Microsoft decided to break that connection, so I was lead to believe, after TFS 2015.
So, I'm wondering, since the linked to PDF speaks of integration between TFS 2018 and SharePoint, what is that about? Especially if TFS team rooms have gone away?
According to this doc about TFS 2018 and SharePoint integration:
TFS 2018 and later versions no longer support integration with SharePoint.
The SharePoint integration supports the TFS 2017 and earlier versions. In TFS 2017 and earlier versions, in addition to the team room function, this integration also has other functions.
For more detailed information about sharepoint integration , you could refer this Blog.
Since you are upgrading the TFS 2015 to TFS 2018, if you have configured the SharePoint integration in TFS 2015, you need to disable the SharePoint integration after upgrade.
In addition, in TFS 2018, we start to use Microsoft teams or slack for monitoring and communication.
Hope this helps.
Think this MS-Post might give you the answers: The future of TFS/Sharpoint Integration
I've been looking for some details about Team Foundation Server 2018:
a) How many projects can I have for collection (maximum) ?
b) Is Power Tools 2015 totally compatible with TFS 2018?
Now I've been trying to find out something related to this 2 topics in the Microsoft Documentation which is important to me.
Concerning this 2 question can anyone point me in the right direction? Because I cannot find the right documentation for this.
Thanks.
a) How many projects can I have for collection (maximum) ?
As comment mentioned clearly, currently there isn’t any official document to be referenced for the team project limits in TFS 2018.
Below is the recommended limit for Team Projects and Team Project Collections in TFS 2010, and you can refer to the numbers for your TFS structure.
200 Team Projects per Team Project Collection 50 – 200 Active Team
Project Collections per SQL Instance (range for 8GB – 64Gb of RAM)
From Martin's blog, there is a soft limit of about 300 Team
Projects per Team Project Collection in TFS 2012.
You can also reference the old document for the limits: Team
Foundation Server Team Project Limits
b) Is Power Tools 2015 totally compatible with TFS 2018?
There is no set of TFS 2017 Power Tools/Visual Studio 2017. Since from the TFS 2017 release notes.
No Power Tools have been released for TFS 2017. Most of the previous Power Tools have been integrated into TFS 2017, same with TFS 2018.
You could still use Power Tolls 2015, it's not related to TFS version. It's also compatibility with TFS 2018
Compatibility
You need to match the version of the TFS Power Tools with your Visual
Studio client. If you have VS 2015 installed, you need to install the
TFS 2015 power tools. Regardless of which version of TFS you are
targeting.
Source Link
In respect to the following question Is there a way to easily share Workspace settings (folder mappings) for Visual Studio Online / Team Foundation Server? and an entry I found regarding to this topic https://social.msdn.microsoft.com/Forums/vstudio/en-US/c9b16b30-4534-4781-a2e8-fb413a2df0af/power-tools-for-tfs-2017-with-vs-2017-rc?forum=tfsgeneral I wanted to ask if anyone knows how to achieve this very much needed functionality in TFS 2017?
Thanks.
Unfortunately we cannot create the workspace templates with VS 2017 for now.
According to release notes it says most of the previous Power Tools have been integrated into TFS 2017 that means no separate power tools for TFS 2017.
But the Team Utilities feature component is not integrated, that means these haven't shipped for Visual Studio 2017.
I have submitted a user voice here for you to suggest this feature, you can go and vote it up to achieve it in future.
Another similar thread for your reference: Team Members Team Utilities section in VS 2017
First day trying new VS Community 2015 RC Version 14.0.22823.1 D14REL.
Our TFS server is still TFS 2010; I'm wondering if that's the source of the problem.
Other Team Explorer sections are working fine -- Work Items, Source Control Explorer, Pending Changes. I even did a merge and checkin successfully.
But the Builds section shows this:
I'm not even sure where to look for an error log.
VS.NET 2012, still installed on the machine, shows the Builds section correctly.
As support for TFS 2010 ends before VS 2015 releases don't expect the support to be awesome. If you don't have SP1 then your are already out of support. None of the editions of Visual Studio 2015 (and 2013) officially support TFS 2010 RTM.
I would recommend that you upgrade to TFS 2013, or TFS 2015 at your earliest opportunity. If you need support for that then get a consultant to help who has a good relationship with MSFT.
If your ops team is inside of keeping software up to that's and with the applications support model then you should seriously consider moving to VSO so that you don't have to worry about It any more.
Reinstalling VS 2015 after my Windows 10 debacle, I found that suddenly everything was working including builds! With the server still on TFS 2010. Apparently my problem was that I had the VS 2015 Community Release Candidate, not the final release.
I'm running TFS client 2013 with Visual Studio 2013, TFS Server 2010.
I've installed TFS Power Tools 2013 but I am unable to locate Alerts Explorer
How do I open Alerts Explorer or is there some configuring I am missing?
Edit:
I know that in TFS 2012 and 2013 this is part of the product but I still need the functionality while using TFS 2010 with a more recent version of Visual Studio. Is there a way to have that functionality? The default Project Alerts functionality which is built-in is useless as it does not provide any control.
Hate to be a buzzkill but what you are trying to do simply will not work. There is no Alerts Explorer present in the Visual Studio 2013 client, even with the TFS 2013 Power Tools installed. Why? It appears they moved this functionality into the TFS 2013 web access so they didn't include it in the VS 2013 client. The VS 2013 client is not backwards compatible with TFS 2010 with respect to managing alerts.
The Alerts Explorer is a feature of TFS 2010 Power Tools. What you need to do is install the Visual Studio 2010 Team Explorer shell (http://www.microsoft.com/en-us/download/details.aspx?id=329) and then install TFS 2010 Power Tools on top of that. It's going to be a pain to have to boot up the VS2010 shell just for alerts management but there's pretty much no other option. In case you are wondering the VS2010 shell looks just like VS2010 but it only contains the features for connecting to TFS. It's free... no licensing fees, etc.
Microsoft states this pretty plainly even though they use the word "might"...
Q: How do I manage alerts when I connect to TFS 2010?
A: The instructions in this topic require you to connect to TFS 2012 or TFS 2013. If you have upgraded to VS 2012 or VS 2013 and are connecting to TFS 2010, then you might have to install Team Explorer 2010 side-by-side to manage alerts stored on TFS 2010.
Reference: http://msdn.microsoft.com/en-us/library/ms181334.aspx
You can also get to the alerts via Visual Studio using the menu. Team > Project Alert. This will navigate to your TFS web access (something like http://tfs:8080/tfs/TFS/PROJECT/_Alerts).
You don't need it anymore, that functionality is now part of Team Foundation Server 2012 and 2013.
In TFS Web Access click on your Name (top-right) and go to My Alerts -> Custom Alerts -> Other