I have applied v12 patch to our tfs 2017 v3.1 installation 15.117.27414.0. Why does the patch version not get shown in the tfs gui or in the tfs admin console ?
I was expecting to see 15.117.30801.0 but it still shows 15.117.27414.0. Can anyone explain, thank you
15.117.30801.0 is the version of file Microsoft.TeamFoundation.Server.WebAccess.Admin.dll. If the installation of TFS 2017 Update 3.1 Patch 12 is successful, you'll see the version of file Microsoft.TeamFoundation.Server.WebAccess.Admin.dll is 15.117.30801.0. TFS 2017 is installed to c:\Program Files\Microsoft Team Foundation Server 15.0 by default, the file Microsoft.TeamFoundation.Server.WebAccess.Admin.dll is in [TFS_INSTALL_DIR]\Application Tier\Web Services\bin\Microsoft.TeamFoundation.Server.WebAccess.Admin.dll.
Related
I have installed the vsBuildTools for 2022 in order to assemble a build machine. The build tools do not come with TFS tools to actually download source code.
Where can I get the TFS parts to finish this build server? (I did not want a full Visual Studio 2022 install if possible)
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.
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.
I've installed visual studio 2017 enterprise and the new stand alone Team Explorer 2017. There doesn't seem to be an option in either to add tfs command line tools or tfs shell integration. this implies that it's an extension, but I haven't found anything on the visual studio marketplace. I'd prefer not to reinstall 2015 to use the 2015 power tools, but there is no tf.exe anywhere on my box.
According to TFS 2017 RTW release notes, most of the previous Power Tools have been integrated into TFS 2017, that means no separate power tools, you don't need to install that separately. The Process Template Editor is one that has not been integrated, but you can get it in the Visual Studio Marketplace.
Visual Studio 2017 users: The tf.exe binary is no longer in a fixed
location in the Visual Studio install path as in previous releases
(for example, C:\Program Files (x86)\Microsoft Visual Studio
14.0\Common7\IDE). Scripts using tf.exe should not hardcode a path to the file based on the Visual Studio 2017 install path.
Just as mentioned by Dave, the tf.exe should be under the path :
C:\Program Files (x86)\Microsoft Visual Studio\2017\{Version: Enterprise,Professional,Community}\Common7\IDE\CommonExtensions\Microsoft\TeamFoundation\Team Explorer\TF.exe
In most cases, you run the version control command in the context of a directory that is mapped in the workspace. For example, $/SiteApp/Main/ is mapped to c:\\code\\SiteApp\\Main\\. To get the latest version of all items in the workspace:
c:\code\SiteApp\Main\SolutionA>tf get
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.