Skip to main content

TFS Build: output build results to separate folders

By default TFS Build will redirect the output of your projects to one location(specified by the BinariesDirectory parameter). This means that all DLL’s, executables and so on are available at one place. However the Sharepoint team asked me to change this so that TFS build put each project output into its own folder, instead of dropping all of the files into one flat structure. They wanted the same behavior as in Visual Studio so that the files are available under e.g. Bin\Release, Bin\Debug, etc… This makes it easier for them to run WSPBuilder and create deployment packages.

So how can we do this?
  • Open the Build Process template you are using.
  • Drill down until you find the “Run MSBuild for Project” task used to execute the MSBuild process.

image

  • Set the OutDir property to an empty string. The OutDir property over writes the default output path on each project. By clearing the OutDir property for the MsBuild Activity, Team build will use the Output Path defined in the project.

image

  • That’s it!

Remark 1:

If you want to have a reference to the default TFS outputdirectory, you can pass an extra property to MSBuild by setting your CommandLineArguments to something like the following. String.Format

("/p:SkipInvalidConfigurations=true /p:TeamBuildOutDir=""{0}"" {1}", BinariesDirectory, MSBuildArguments)

Inside your MSBuild files, you now have an extra property that you can use: $(TeamBuildOutDir).

Remark 2:

If you also want to copy the build output to the binariesdirectory, you’ll have to create some extra activities. For some help how to do this, check out this blog post.

Labels:

Popular posts from this blog

Podman– Command execution failed with exit code 125

After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...
Read more

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.
Read more

VS Code Planning mode

After the introduction of Plan mode in Visual Studio , it now also found its way into VS Code. Planning mode, or as I like to call it 'Hannibal mode', extends GitHub Copilot's Agent Mode capabilities to handle larger, multi-step coding tasks with a structured approach. Instead of jumping straight into code generation, Planning mode creates a detailed execution plan. If you want more details, have a look at my previous post . Putting plan mode into action VS Code takes a different approach compared to Visual Studio when using plan mode. Instead of a configuration setting that you can activate but have limited control over, planning is available as a separate chat mode/agent: I like this approach better than how Visual Studio does it as you have explicit control when plan mode is activated. Instead of immediately diving into execution, the plan agent creates a plan and asks some follow up questions: You can further edit the plan by clicking on ‘Open in Editor’: ...
Read more