I have VS 2017 and VS 2019 installed on my computer. When I compare my changed code in VS 2019 Team Explorer's Pending Changes window, the differences are shown in VS 2017. That is as soon as I choose Compare with Latest Version option from context menu, VS 2017 is started and differences are shown in VS 2017. Is it something that I have to change in VS 2019 settings or VS2109 is supposed to work like this?
No, it's not an expected behavior.
Have tested VS2019 with either VS2017 or VS 2015 installed, both worked properly.
This strange behavior may related to cache. I was wondering if your target Path used to open under VS2017 in your environment. Or something cached in VS2017.
Please try to clear TFS cache and VS cache which may do the trick. First with TFS cache, if not work then with VS cache.
Related
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:
Our company is stuck on TFS 2013 due to Adobe's RoboHelp software only working with that as a maximum version. We are looking to migrate to .NET 4.6 from 4.0 and VS 2017 - As such we can use new framework featuers (such as Async / Await) and language features (Like Tuples).
Unfortunately our team build is failing when building a test project with the upgraded stuff and I assume this is because it's pointing at the 4.0 MSBuild.
I've installed VS2017 (Compiler and .NET 4.6 targeting pack). I have done some research on the topic but TFS 2013 + VS 2017 seems an oddly specific combination. I did however find that I need to change the ToolsVersion to 14.0 which I have done.
MSBuild then shows me that the maximum ToolsVersion I can have is 12.0, which again makes me think I'm using an old MSBUild. More research lead me to the ToolsPath property which I have set to "C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\MSBuild\15.0\Bin". However this still gives me the same error.
How do I go about getting VS 2017 projects to build on TFS 2013? I presume I need some kind of MSBuild path changing but the ones I have tried so far just don't seem to cater for the new syntax.
Just for anybody else that comes across this issue - There are potentially multiple MSBuild tasks within the build process template, I happened to have two and as soon as I changed the ToolPath on the second task to the full MSBuild path, my project started to build.
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.
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 hosted my TFS on visualstudio.com but I can't seems to find the tfsconfig on my local machine and unable to enable codeindex from the web interface. Anyone has similar issue?
Update
April 17th this year Codelens is now live for all accounts on Visual Studio Online.
Requires:
Visual Studio 2013 Ultimate with update 4 or higher for TFVC
Visual Studio 2013 Ultimate with update 3 or higher for Git
Visual Studio 2015 Professional or higher for TFVC and Git
In case this doesn't work:
Close all instances of Visual Studio.
Delete all the cached data in the folder %localappdata%\Microsoft\VisualStudio Services\5.0\
Restart Visual Studio and re-open the solution from Visual Studio Online.
There is an update!
Currently CodeLens is being developed for VSO, currently in Public Preview for what I have read so far, in US and West-Europe.
Requirements:
Be using Visual Studio Ultimate 2013 Update 4, or Visual Studio 2015
(Preview or later version).
Check your code into Team Foundation
Version Control in Visual Studio Online.
Just updated to VS Ultimate Update 4, already had a solution setup on VSO, works great as expected.
troubleshoot, CodeLens not appearing?
Close all Visual Studio Instances.
Remove the cache from %localappdata%\Microsoft\VisualStudio Services\5.0\
Reopen Visual Studio, open the solution from Visual Studio Online.
I'm not sure if it was necessary to do this for me, I did it, looked like it had no effect and the codeLens still didn't appear. While I was typing out a new question they suddenly appeared. So it could take a few minutes.
Source: CodeLens in VSO is now in public preview
I don't believe CodeLens works against VSO yet.