VNext

An object at the specified path C:\Users\user~1.name does not exist

不问归期 提交于 2021-01-29 04:21:14
问题 So today I came across an issue whereby a powershell script was causing the deployment to fail. This job is set-up exactly the same on other machines. This one however just refused to work. The error was: An object at the specified path C:\Users\user~1.name does not exist heres the full log at the time of failure 2017-01-11T15:03:12.1295730Z Executing the powershell script: D:\Tfs\Agent2\tasks\PowerShellOnTargetMachines\1.0.25\PowerShellOnTargetMachines.ps1 2017-01-11T15:03:12.3014605Z ##

TFS 2015 / vNext Build - Set Build.Clean Control Variable in a build step

只愿长相守 提交于 2019-12-24 00:45:21
问题 Is it possible to set the Build.Clean control variable during a build step (Not at Queue Time), based upon the way the build is queued? For instance, I have a build that if queued manually during the day, I want it to run Incrementally. If it runs on its schedule in the middle of the night, I want to have it do a Build.Clean, recreating the Binaries (b) folder on the build agent. It seems like this control variable has to be set at queue time, because the build runs this operation on the

TFS vNext Build: GetSources task does not get files from folder with restricted access

▼魔方 西西 提交于 2019-12-13 19:54:44
问题 we are currently migrating from XAML build to vNext (TFS2017). The "normal" builds work fine, but the build for our LicenseManager does not work. The folder containing the LicenseManager source code can only be accessed from certain users. So I configured one vNext build agent, where the build service runs on an account that has access to the source code (like we did with the xaml build). I used Capabilities and Demands to force the LicenseManager build on that agent. But the GetSources task

How to retrieve a Test Case ID that is currently running through TFS (vNext) build?

。_饼干妹妹 提交于 2019-12-12 04:32:07
问题 In TFS 2013 when running tests from MTM, we were able to get the ID of the currently running test case by using the TestContext Properties dictionary as follows: var testCaseID = TestContext.Properties["__Tfs_TestCaseId__"].ToString(); This statement returns NULL if tests are being run as part of TFS vNext build (BDT). In order to update some fields in test results for instance Comments/Notes, I will need to know the ID of the current test run and test case. How can I return that information?

TFS 2015 vNext Gated Check-in builds are “Waiting for an agent to be requested”?

半世苍凉 提交于 2019-12-11 09:57:07
问题 We are trying to use TFS 2015 Gated Builds. The trigger hooks in correctly, and the build gets created, but it never gets picked up by any agent. Non-gated builds start fine, and if we manually restart the gated build, that runs fine too. But the gated build (the important one), just sits there saying "Waiting for an agent to be requested" and "Waiting for an available agent": No logs get created in the _diag folder for these builds. EDIT: Added screncap of agent: 回答1: Check the table tbl

ASP.NET 5系列教程 (一):领读新特性

北城余情 提交于 2019-11-26 16:02:57
近期微软发布了ASP.NET 5.0,本次发布的新特性需求源于大量用户的反馈和需求,例如灵活的跨平台运行时和自主部署能力使ASP.NET应用不再受限于IIS、Cloud-ready环境配置降低了云端部署的门槛,另外源码开放无疑也是一个重量级惊喜。这些更改会有助于创建易于开发、部署、维护和现代的Web应用程序。相信看到以上几点作为.NET程序员的你已经迫不及待体验ASP.NET 5 的新功能了,下面我们就来看下这些新特性。 ASP.NET 5 是用于创建Web应用的框架,相对于以前的版本它更加简练、灵活,本次发布的版本彻底优化了应用开发框架,你可以轻松部署应用到云端或其他平台,它包含了最小的模块化组件,所以确保你在构建复杂解决方案的同时保持灵活性。 ASP.NET 5 包含以下特性: ·灵活的跨平台运行时 ·新的HTTP模块请求管道 ·Cloud-ready环境配置 ·统一了包含 MVC、 Web API 和 Web 页面的编程模型 ·无需重新编译即可查看更改效果 ·并行的.NET Framework 版本 ·自主部署或IIS部署能力 ·内嵌于Visual Studio 2015中的新工具 ·GitHub开放源码 使用旧版本开发的应用程序不需要做任何修改,即可直接在 ASP.NET 5上运行。然而,如需使用ASP.NET 5 新功能,你需要将现有代码移植到新的框架。ASP.NET 5