tfsbuild

When I build a solution on my build server it generates a binaries folder and then later on copies these binaries to the final output folder. In my case some of the third party assemblies REFERENCES are correctly copied over while other 3rd part assemblies REFERENCES are not copied over. Take not that my solution projects do not directly reference the assemblies being copied over. This means that everything build fine. But when I run my program it doesn't start since the assemblies it's referencing can't in turn load their references. What process in the build determines what assemblies are

We just upgraded to TFS2015 (onsite) and I'm trying to set up a build that will do the same thing as my xaml builds but I can't seem to get the same files built. Here's a picture of the xaml output directory that I use to publish the site. To get this I navigate to the build folder then drill down to the _PublishedWebsites\BOTWSitecoreWeb folder: Here's a picture of the solution explorer: So as you can see BOTWSitecoreWeb is my startup project and it forms the basis for the website. So to publish this website I simply copy the folder: _PublishedWebsites\BOTWSitecoreWeb to my IIS directory.

I'm hitting a weird issue with MSBuild , and I'm thinking it might just be an environment issue. We're using MSBuild to build a number of separate solutions, and it seems to work on my machine. But on a couple of other machines, it's not working. I've tracked down the issue, and it looks like one of the solutions (or one of the projects in that solution) is being built in "Release" when everything else is being built in "Debug". This causes some of the references to be missing - so the solution being built in "Release" fails to build. I want all solutions to be built in "Debug". In the

In Team Foundation Server 2015 in build definition I use my custom variables defined on Variables tab. Is there any way to access them in PowerShell build step like predefined variables can be accessed e.g. "$env:BUILD_DEFINITIONNAME"? Thank you [disclaimer: I work on the new build system] I often advise folks to use the cmdline task or a cmd script to print out the variables (call set on windows, env on *nix). There's docs etc... but actually running it will show exactly what is really available. Add cmdline task (in utility) with tool = cmd and arguments = /k set Variables on the definitions

With the right version of Visual Studio 2012 we can have database compared and synced I'm looking for way to integrate this synchronization process into a TFS build as in Continuous Integration for code; now I need that for database schema and data. Please share if you know how to do it. Dylan Smith Things changed a bit between VS 2010 and 2012. Assuming you're using VS 2012 (the link you posted was to 2010 tech), that means you're using SSDT (SQL Server Data Tools). So long as your SSDT project is part of the solution you've selected to build in TFS Build, it will build and output a .dacpac

I have been scouring the internet for an answer on this and could really use the help. I've already looked at other posts regarding this error and none of those answers helped me. The full error is, The type 'xxx' is defined in an assembly that is not referenced. You must add a reference to assembly 'xxx, Version=0.0.0.0, Culture=neutral, PublicKeyToken=null'. The solution builds fine locally, but the error occurs when I trigger a build on the build server. Here's what I've done so far in an attempt to resolve this: Ensured all project references are correct(Had an Architect review it with me)

I'm trying to do Continuous Integration using TFS 2010 for a Windows Phone 7.1 project. There are 2 resource projects ( Win32 Project for localisation ) and the main Windows phone project. I have copied the project output of above 2 projects to a folder in the main WP project (inside 'MUI' folder) , and also marked the files as 'content' in build action. All works well when building and running the WP7 project from Visual Studio 2010. But when I try to build the projects using TFS 2010 build system , the build fails with the following error "Xap packaging failed. Object reference not set to an