We use Team Foundation Server 2018. Since our upgrade to Visual studio 2019 I have been trying to add this capability to TFS 2018, without any success.
TFS version: 2018 (16.122.27102.1)
I have already tried to reconfigure the Agent, or even add a new one.
Visual studio 2019 is installed on the TFS server + has the same checks as the 2017.
Deleting VS 2017 on the server doesn't help either, no capabilities found then.
Are there any tips/tricks that I need to perform to get TFS working with VS2019 build?
Team Foundation Server 2018 Build agent Capabilities VS 2019
The Visual Studio is generally compatible with newer versions of Team Foundation Server.
You can see the details specified by Microsoft here: Requirements and compatibility.
Only the latest version has "full" compatibility with the latest Team
Foundation Server, because this will be the only client that contains
components that can interface with new features for that release, and
will also be the only client from which you can perform certain
administrative tasks such as creating new team projects.
So, the Team Foundation Server 2018 should be a high level of support VS 2019 not full support.
Team Foundation Server 2018 Agent could not recognize vs2019 and msbuild 16.0 capabilities. Then you could not select the Visual Studio 2019 in the Visual Studio version of VS build task. Because TFS doesn't know how to locate future VS versions
To resolve this issue, you can use MSBuild task instead of Visual Studio Build Step, then specify the location of MSBuild 16.0, it should be:
C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\MSBuild\Current\Bin\MSBuild.exe
Hope this helps.
Related
I am new to TFS and am trying to build an VB project created with Visual Studio 2008 using Team Foundation Server 2017 Build feature.
As you can see on the image below, I need to set the Visual Studio version on the Build Solution task and there is no dropdown option for Visual Studio 2008.
Is there anyway I can select VS 2008 to build this project?
Or is it possible to do this?
I will appreciate of any help I can get.
Based on the information provided from Microsoft at TFS Server Requirements, and specifically looking into the Client Compatibility / Visual Studio 2008 falls under the MSSCCI support category:
MSSCCI support
Visual Studio/Team Explorer 2008 and Visual Studio 2005 are no longer officially supported. To connect to the server, these clients must interface through the MSSCCI provider instead. MSSCCI support only includes support for source control integration and MSSCCI commands. The goal is simply to allow developers to continue working with legacy applications in an upgraded server.
I believe that, if you have to stick with Visual Studio 2008, you could use MSBuild step instead, and specify the proper location of the MSBuild 3.5, and verify if this would work for you:
After upgrade of Visual Studio 2017 last week on my build server, the MS Build 15.0 is not in use anymore. So whenever I try to compile visual studio 2017 projects which use new feature they will fail.
The Warning in build log is:
Visual Studio version '15.0' not found. Looking for the latest
version.
And the error is:
something.cs(542,41): Error CS1525: Invalid expression term 'int'
Which is because build server is using MS build 14.0 I guess.
So far I have
1- Uninstall and Reinstalled the Visual Studio 2017 on the build server.
2- Installed "Visual Studio Build Tools 2017".
And nothing works.
I have read some articles and apparently there are missing registry values but I don't know how to create them.
Appreciate your helps on this topic.
I am using TFS 2017 SP1 (On premises) and Visual Studio 2017 latest updates.
This may due to the VS is installed after the build agent configured. Then reregister the build agent with TFS, since the system capabilities are only discovered when the agent is first configured -- any changes made after that are not captured.
More ways please refer this similar question: No agent could be found with the following capabilities: msbuild, visualstudio, vstest?
Or install the latest version of the agent for now, which appears to be capable of detecting VS2017.
Also remember to select VS2017 in Visual Studio Version picklist of Visual Studio Build task.
I have resolved this issue by upgrading my TFS from TFS 2017 SP1 to
TFS 2017 SP2.
Thanks to #Patrick-MSFT and #Martin Ullrich for your help.
In VS 2015 I had this that could install some check-in policies with it:
But in VS2017 I can't find it. Where has it gone?
That came as part of the Visual Studio Team Foundation Server Power Tools. These haven't shipped for Visual Studio 2017.
How do I get the TFS options to appear in Windows Explorer?
I have the Power Tools installed and for a few of my projects I do have the TFS options available in Windows Explorer.
I have recently created a couple of new branches from my Main project, but these new branches do not have the TFS options when "Right Clicking" the folder from within Windows Explorer.
I have tried reinstalling Power Tools, but this has not fixed my issue.
Does anyone know how I can get the TFS options to appear for my new projects in Windows Explorer?
If it makes a difference to the answer: I am using VS2008 with Power Tools 2010.
I cannot use a newer version of VS.
If you are using Team Foundation Server Power Tools December 2011 in your environment. You could try this solution: Uninstalled the old TFS Power Tools ( listed with a "Microsoft Team Foundation Server" prefix and/or "Microsoft Visual Studio Team Foundation Server" in Control-Panel/Programs-and-Features ) and install a newer version. Such as:
Team Foundation Server 2012 RTM Power Tools.msi
You could also try to execute this file:
C:\Program Files (x86)\Microsoft Team Foundation Server 201X Power
Tools\TfsComProviderSvr.exe
More detail ways please refer this similar question: Shell Extension : Not showing in Windows Explorer context
I have TFS2012 Update 3 server. We have started new VS 2013 project. I need to prepare build server and service. My initial thought is to install Vs 2013 together with TFS2013 build service.
After installation TFS2013 and registration to TFS collection I got below issue:
The register command is not supported for Team Foundation Service [our_tfs_url] because the server is not compatible.
Please advice any solution how to create builds for VS 2013 projects that are stored in TFS 2012.
Update 1:
1) I installed TFS 2012 build service and redirect msbuild ( toolpath) in build template to use VS 2013 msbuild
2) I am able now to build project with a test
3) There are still issue with Code Coverage, that finish with warning: Install visual studio. It seems for me that CC used still VS 2012. Is any way to redirect CC to VS 2013?
Below solution helps me build on VS 2013 build machine with TFS 2012 build service and generate code coverage.
TFS 2012 buid service runs tests from 11.0 location, to replace CommonExtensions in folder
C:\Program Files (x86)\Microsoft Visual Studio 11.0\Common7\IDE\CommonExtensions
with Vs 2013 assemblies from
C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE\CommonExtensions
fix that issue and now I can see code coverage per build.
thanks MS to provide workaround on that issue with Code coverage.