My team is performing an analysis on which TFS version to upgrade to (from 2010).
One issue that we have faced daily is that TFS 2010 will log pending changes on files that are unchanged. For example, if I edit the JavaScript on HomePage.aspx, while leaving HomePage.aspx.cs and HomePage.aspx.designer.cs unchanged, the later two files will still log as pending changes, resulting with 3 files in the pending changes tab.
This post addresses this issue, and even has a semi-appropriate answer. But I'm wondering, has this issue has been fixed in terms of using TFS 'out of the box' with TFS 2017 or 2018? Do I really need to use TFS Power Tools with the latest version of TFS to get around this annoyance? I see many people saying that Power Tools doesn't solve the issue for all configurations.
That's Visual Studio behavior, not TFVC. I would expect that the behavior will remain the same regardless of the version of TFS you use.
That said, you should upgrade to 2018, period. There's no benefit to upgrading to a version that's already supplanted by a newer major release.
#Daniel is correct. This behavior remains no matter which version of TFS you are using. You could see HomePage.aspx.cs and HomePage.aspx.designer.cs belong to HomePage.aspx, TFS treats them as one file. If you check the history of HomePage.aspx.cs and HomePage.aspx.designer.cs, you'll find no new history produces, as during check-in, TFS detects there is no changes for these two files:
Related
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 noticed that I can change the order of the PBIs of the current sprint on visualstudio.com via Drag&Drop. At work we use TFS 2013 on our own server (I think the newest version Update 4) and that's not possible. Both use the SCRUM template.
Is this a configuration issue? It would help a lot if this would work at our own TFS too. What should I do?
The features available in VSO are beyond that of TFS 2013 update 4. The feature that you are referring to is planned for TFS 2015.
https://www.visualstudio.com/en-gb/news/release-archive-vso
For most customers, regardless of size, I recommend moving to VSO to get access to the latest and greatest features as they become available.
I was setting up a new build definition today and noticed there is an option 'Copy build output to the following Source Control folder'. I don't believe I have seen this before. It appears to me from searching google that it might be new as of TFS 11 (AKA TFS 2012) which I do not have installed on my system (or any system in my company network to my knowledge). My company uses TFS 2010 right now.
I went to another user who is able to view build definitions and it also was present when the build definitions were viewed.
This is what i see:
My questions:
1) Was this a part of TFS 2010 and I am just not remembering seeing it?
2) If this IS part of TFS 2010, how to enable this option (it is disabled).
3) If this is NOT a part of TFS 2010, how did it get there?
Yes, it is part of TFS 2010, but I have no idea how it got here!
I believe this is for those who use TFS 'as a service' (when you
have no file share to copy it to). According to
how-can-i-copy-build-output-to-the-source-control-folder
I have this in TFS/VS 2010 (SP1):
I wish we could use multiple build controllers on the same machine because we have many team project collections but they're not used at the same time so there's no real performance issue here and most of our build servers are not used for extended period of time. I know it's possible to do this with TFS 2010 and TFS 2012 (see following post) but it's an unsupported feature.
Anyone can tell me if it's now officially supported with TFS 2013, I've not been able to find any useful information about this.
This is still an unsupported feature. This feature would be loudly trompetted should it arrive.
On the chances of this arriving in the TFS 2013 updates, I don't expect it. Maybe with TFS v14 (they're skipping v13) or maybe the version after that?
Make your voice heard on UserVoice:
http://visualstudio.uservoice.com/forums/121579-visual-studio/suggestions/2037679-remove-one-one-binding-between-collection-and-buil
http://visualstudio.uservoice.com/forums/121579-visual-studio/suggestions/4417771-use-a-build-controller-over-more-than-one-team-pro
http://visualstudio.uservoice.com/forums/121579-visual-studio/suggestions/3872254-tfs-2012-possibility-to-have-more-than-one-build
Update
A new build system was introduced in TFS 2015 and Visual Studio Team Services. It's agent based. doesn't have Controllers and you can install multiple agents on a single machine.
Agents are grouped in Pools and live at the Server level, allowing you to use them across collections.