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.
Related
We have TFS 2013 SP 4 (our existing version) and TFS 2017 (which is under testing for we are upgrading the TFS version).
My question is : Is it possible to work and test on both the TFS at the same time with the same workspace?
Business users are able to configure the new TFS 2017 and work there. However, when they are switching back to TFS 2013 (since we have not gone live with TFS 2017), it throws an 'Identity does not exist error'.
Has anyone tried it?
Is it even possible to test this way? Or shall we have one TFS version at a time for one workspace even for testing?
Thank you.
Anant
When upgraded TFS 2013 to TFS 2017(using TFS 2013 backup) on a new Server, the two servers have the same TFS GUID, which will confuse your Visual Studio clients.
You should avoid having two TFS up & running with the same set of GUIDs. And this is usually avoided by shutting down the old TFS server after the upgrade has finished and has been tested & verified.
We currently have a TFS 2012 Server which is being replaced by a 2015 server, the aim is to gradually migrate our code from one to the other.
When we do this we would like to maintain the checkin history, labels etc, Looking at similar questions the answer seemed to be to use the integration toolkit, however it looks like it (and its successor the integration platform) do not support TFS 2015.
We are using TFVC rather than git, if that makes a difference.
I don't have much knowledge about the integration toolkit, but I would actually suggest to do the upgrade one Team Project Collection at a time, but moving them separately to a new server with TFS 2015 installed. This way you will keep all history, label etc.
We have done this way back when upgrading from TFS 2010 to TFS 2013. Only obstacle that we had was a collection around 500 GB in size so it took around 16 hours for the upgrade to finish.
The following answer specifies the steps needed to move a collection to another server:
Copy TFS 2012 collection to another server with TFS 2015 Installed
We have used this Migration tool for our Client.
It’s possible to migrate TFS 2012 data to TFS 2015 with all information intact without any system downtime. The premium version of OpsHub Visual Studio Migration Utility (OVSMU) supports migration of projects with TFVC repository from one instance to another. It supports the 2010, 2012, 2013, and 2015 versions of TFS and all versions of Visual Studio Online, including the 2017 version. Along with basic data, you can migrate all workitems with history, comments, attachments, relationships, and source control with changesets, history, labels, comments, etc. You can checkout the details here: https://www.opshub.com/products/opshub-visual-studio-migration-utility/
I installed Visual Studio 2015 Enterprise RTM and only seeing "references" from Code Lens. We are using TFS for source control. I expect to see related commits from TFS. Based on this article, I have everything enabled in options:
Here is what I see in VS:
Is there anything wrong with my VS setup?
The TFVC lenses that are part of CodeLens only work when connected to a version of Team Foundation Server that is running the background job that generates the historical data. This means that you need to be running at least TFS 2013 or 2015 in order for this feature to work. Some features require a specific version of Visual Studio.
It is also possible that your server admin has disabled indexing on the server, one can do that using the tfsconfig codeindex command on the application tier.
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
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