tfsbuild

问题 I'm running a CI build on a TFS build controller, connected to VS Online. I've got a 'Could not resolve this reference' problem for a NuGet package and I've observed behavior that I haven't seen before: Locally the pacakage is downloaded to packages\FluentValidation.5.5.0 whereas on the server, it's downloaded to packages\FluentValidation.5.5.0.0 . Packages.config: <package id="FluentValidation" version="5.5.0" targetFramework="net45" userInstalled="true" /> .csproj file $(SolutionDir) for

问题 I am having issue with TFS build server 2013, where during the build process, it fails to copy certain files, while the files exist in the TFS repository. C:\Program Files (x86)\...\v12.0\..\Microsoft.WebApplication.targets (182): Could not copy the file "www\public\modules\xxx.tmpl.html" because it was not found. The files do exist and have been accessed and modified by multiple developers, all using VS 2013 pro. Would anybody have encountered this before? Thanks in advance. 来源： https:/

问题 I have a Powershell script that needs to set a custom build variable, such that it can be used in a later task. I have successfully added a variable, and verified it can be accessed and set from Powershell, but, for whatever reason, the change does not persist when referencing the variable in a later build step. Write-Host $env:VERSIONNUMBER #prints the variable value set in TFS Build $env:VERSIONNUMBER = 'This doesn't stick' Write-Host $env:VERSIONNUMBER #prints 'This doesn't stick', but not

问题 I'm trying to configure a new install of Team Foundation Server Express. The problem I'm having is that when I run a build that outputs to a drop folder I get the error An error occurred while copying diagnostic activity logs to the drop location. Details: Access to the path '\\c$\drops\Test Application\Test Application_20130206.9\Logs' is denied. If I disable the drop folder the build runs fine. The drop folder is located on the same machine as TFS. I've given full control of that folder to

问题 I have been staring at this problem all day and I'm completely baffled by what I'm seeing. There are two issues occurring, and unfortunately, one of them only happens in Production so I can't test it the way I'd like. I will give all the background and relevant information up front with the code at the end. Some of what I say in these next couple sections won't make much sense until you review the code. Background info: (I have triple verified all this information) This class is being called

问题 When trying to create a new build definition for my Team Project, I got the below error. I check and see that the build controller is running. How can I get around with this? 回答1: As per your other question: Cannot select the TFS build service for more than one team project collection This is a known limitation of Team Build. Each Build Controller can only be assigned to one TeamProjectCollection, but you can install multiple Build Controllers (although you can only install one Build

问题 I have created a new build definition with a custom activity. I modified the AzureContinuous deployment xaml as explained here: http://www.ewaldhofman.nl/post/2010/06/01/Customize-Team-Build-2010-e28093-Part-10-Include-Version-Number-in-the-Build-Number.aspx And here a problem I had before but I could solve it: 'AssemblyInfoFileMask' is not declared. It may be inaccessible due to its protection level When I queue a new build I got the exception The path $/FullStackSampleApplication is not a

问题 I am having trouble getting my builds to run when using MSBuild in Team Foundation Server 2015. We are hosting the application on an internal server. I have configured the Controller and Agent, which seems to be okay. The "Visual Studio Team Foundation Build Service Host 2015" service is running. When I try to queue the build, I get the following message, even though I am not using Visual Studio Online: When I ckick OK, the build seems to be queued, but I see the following message forever:

问题 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

问题 When we do a TFS Build, can we alter the build output so that the output is limited to only the changes so that deployment payload is reduced ? Example: When I build a solution, I should only get the changed dlls not all (which includes Microsoft and other 3rd party dlls which are never changed. Configure CI solution in TFS 2015, and unchecked clean options, Since TFS 2015/2017 always delivered all files - changed and unchanged, but I need only changed. This trick doesn't solve the issue: