tfs2015

TFS 2015 SDK Missing Microsoft.WITDataStore64.dll

由 纵饮孤独 提交于 2019-11-27 06:42:55
问题 I am attempting to switch to the TFS 2015 SDK dlls (Version 14) for a few reasons. First, they are in nuget and second, the 2013 SDK dlls (Version 12) require the 32-bit flag flipped in IIS. I pulled down nutget package and the namespaces all line up with the existing version 12 namespaces. Everything compiles fine and there was no error on local deployment. However, when I attempt to load projects using the WorkItemStore service. TfsTeamProjectCollection collection = new

No test found. Make sure that installed test discoverers & executors, platform & framework version settings are appropriate and try again

由 大城市里の小女人 提交于 2019-11-27 05:41:27
问题 I am in the process of upgrading our existing solution to .Net 4.6.1 and have been unable to get our unit tests to run during a server build. Locally they run as expected and flipping the framework version back to .Net 4.5.1 makes them run again on the server. I am getting the following error: No test found. Make sure that installed test discoverers & executors, platform & framework version settings are appropriate and try again. I have reproduced the problem in a simpler setup: Solution with

How to get TFS2015 Build (Build.vnext) and NuGet package restore to use custom package sources

由 一笑奈何 提交于 2019-11-27 04:36:55
I'm trying to get our TFS2015 Build ( TFSBuild vnext ) going along with VS Team Services. Thus far most blogs and documentation has been helpful, except for when trying to build a project that uses custom package sources for NuGet automatic package restore. I've successfully deployed an a Team Services Build Agent (the new mechanism for builds) and all seemed to go well until the build task to Restore NuGet packages failed. The failure was due to custom/private package source not being picked up from the installed VS configuration, so those packages could not be found. The traditional packages

How to fail the build from a PowerShell task in TFS 2015

由 血红的双手。 提交于 2019-11-27 02:05:44
I am trying to make a certain result in a PowerShell script fail the build process, but its not working for me. I am using the new build actions from TFS 2015 and tried the following options: Logging commands exit 1 I do get red text in the log window of the step as well as marked 'Issues' in the build overview, but the build result is still Green: 'Build succeeded' I want to use the failure in the script to fail the build and thus send an email using an alert on failed builds. Edit: including the PS script: Param( [string]$url ) if ($url -eq '') { #use default value $url = 'https://myurl.com'

TFS 2015 REST API Authentication

由 [亡魂溺海] 提交于 2019-11-26 18:34:46
问题 We are trying to invoke the TFS 2015 REST API's from a web-page using Javascript and have a challenge in establishing valid authentication with the TFS server. We do not know how to generate a personal access tokens or an OAuth access tokens. The instruction below seem to apply more toward VSO than on-premise TFS. https://www.visualstudio.com/en-us/integrate/get-started/rest/basics How can I generate an authentication key/token? UPDATE: As on Mar 2017, the latest release of On-Prem TFS

Where can I find Microsoft.TeamFoundation.Build.Client in Visual Studio 2015?

由 一世执手 提交于 2019-11-26 15:39:45
问题 I have a clean windows installation with just Visual Studio 2015 installed and I'm looking to find the Microsoft.TeamFoundation.Build.Client assembly? I'm wondering if it has now been made obsolete with the upcoming vNext Build or if the namespace moved? or something else? The MSDN documentation only goes up to Visual Studio 2013 and search for the dll on disk produced no results. when I move to VS2015 and TFS2015 id wish to continue to use the classic build system - I guess I could use the

How to get TFS2015 Build (Build.vnext) and NuGet package restore to use custom package sources

由 南楼画角 提交于 2019-11-26 11:12:34
问题 I\'m trying to get our TFS2015 Build (TFSBuild vnext) going along with VS Team Services. Thus far most blogs and documentation has been helpful, except for when trying to build a project that uses custom package sources for NuGet automatic package restore. I\'ve successfully deployed an a Team Services Build Agent (the new mechanism for builds) and all seemed to go well until the build task to Restore NuGet packages failed. The failure was due to custom/private package source not being picked
订阅 tfs2015