tfsbuild

问题 As part of our build process we deploy our web applications using MSDeploy. This worked perfect until a few weeks ago (I think when we updated our build/TFS server to SP1 of TFS 2010). In our build definition there is a step to invoke a process. This process will call the generated deploy.cmd file and passes in a couple of additional parameters. This worked fine for a long time, but now we get this: Error: Unrecognized argument '"-skip:objectName=filePath,absolutePath=.*cmsservices.config"'.

问题 In my tfs build I've created an argument to which I pass in $(TF_BUILD_BUILDDIRECTORY) Then in my xaml file I've added a variable called "test1" and added GetEnvirenmentVariable" step where I would like to store value of TF_BUILD_BUILDDIRECTORY I can NOT get the value to come through. Output from my build: It prints $(TF_BUILD_BUILDDIRECTORY) instead of "C:\temp... etc" Please help! thanks 回答1: Refer to the last paragraph in this MSDN document: Use environment data from a custom build process

问题 In short, the requirement is to verify that our latest released software can be built and then installed after the latest Windows updates and/or other patches were applied. So the build server VM(s) will be configured just for this purpose and the build only needs to run after an update. Since such updates usually are followed with a restart, I am thinking of a server restart event triggering a build and deployment. Does such option exist in TFS 2017? If there is no way to do it through TFS

问题 I am attempting to build a C++ project in a Visual Studio 2013 solution on TC 8.0.6 (build 27767). I have installed the latest MSBuild "Microsoft Build Tools 2013" stuff (which is normally installed as part of VS 2013 install) directly on the server. But I get the following error: [17:05:23]VCTargetsPath is c:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\ [17:05:23]PlatformToolset is v120 [17:05:23]VCMessage [17:05:23]c:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\Platforms\Win32

问题 I am attempting to build a C++ project in a Visual Studio 2013 solution on TC 8.0.6 (build 27767). I have installed the latest MSBuild "Microsoft Build Tools 2013" stuff (which is normally installed as part of VS 2013 install) directly on the server. But I get the following error: [17:05:23]VCTargetsPath is c:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\ [17:05:23]PlatformToolset is v120 [17:05:23]VCMessage [17:05:23]c:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\Platforms\Win32

问题 here's the scene: We use Visual Studio Online and an on-premise build server in our company network with TFS 2013 to build our solution after gated check-ins and releases. Now we upgraded from Visual Studio 2013 to Visual Studio 2015 Enterprise and upgraded to the new .NET version. We are were really eager to make use of the new features of C# 6 but after the first check-in we experienced that the build failed. (Sorry no image here as I have a lack of reputation) Exception Message: MSBuild

问题 I get this error when trying to build a project using Team Build (MSBuild) on TFS 2010: C:\Windows\Microsoft.NET\Framework\v4.0.30319\Microsoft.Common.targets (1970): Cannot import the following key file: CCC.pfx. The key file may be password protected. To correct this, try to import the certificate again or manually install the certificate to the Strong Name CSP with the following key container name: VS_KEY_C00C673BBB353901 C:\Windows\Microsoft.NET\Framework\v4.0.30319\Microsoft.Common

问题 I've set up an in-house NuGet repository (a shared folder on one of our servers), and have added it to the "Available Sources" list in the Visual Studio NuGet settings on my PC. I'm able to successfully install a package into my solution from this repository. However on the TFS server the build is failing because it can't restore this particular package (message: "Unable to find version 'xxx' of package 'xxx'"). The solution is configured for "enable NuGet package restore", which works fine

问题 I'm setting up a new build server to support a migration of our development team from VS2010 to VS2013. We are not migrating our TFS server just yet so the new build server has been set up as a VS2010 Build Controller with 2 Agents. I have also installed VS2013 on the machine (sledge hammer approach). All our code has been migrated to target .Net 4.5.1 and compiles fine on a developer's workstation. Most of our solutions build fine, except the solution that contains web projects. These

问题 A gated check-in will create a change-set whose name is ended with ***NO_CI***? What is that NO_CI stand for? I can just think of "no check in errors" but it doesn't make sense. 回答1: It stands for No Continuous Integration . Since the check-in is gated, the existing code, plus this check-in, will be built separately and only allowed onwards if the build is successful. So when the gating process actually submits it to source control, there wouldn't be any point for that check-in to cause