10

We have just upgraded from TFS 2010 to TFS 2015 and I'm recreating a XAML-Build-Definition in the "vNext" build/workflow-format.

In the old Build it was possible to output all files (the DLLs) flat in one single directory, without their original directory structure.

Is this still possible with the new TFS 2015 Build framework?

I have the following Publish Build Artifact-Settings:

Artifact Type: File Share

Path: \\server\tfslib\$(Build.DefinitionName)\$(Build.DefinitionName)_$(Build.BuildNumber)

The problem is that the original solution directory structure is preserved in the output directory specified in Path. How can I get the output without the whole subtree?

As a workaround I'm currently doing this with a Powershell step after the Publish Build Artifact but it would be nice to do this during the publishing process itself.

jessehouwing
  • 106,458
  • 22
  • 256
  • 341
ovm
  • 2,452
  • 3
  • 28
  • 51

3 Answers3

7

You can use the "Copy File" task and specify the Source Folder in it to achieve this feature. See this question for details: Copy one file in target directory on deploy from visual studio team services

Community
  • 1
  • 1
Eddie Chen - MSFT
  • 29,708
  • 2
  • 46
  • 60
4

This is still possible, you can pass the following command line argument to your Visual Studio Build or MsBuild task:

/p:OutputPath="$(Build.BinariesDirectory)"

This will instruct the build task to redirect all output to the Binaries Directory, as you were accustomed to from the old XAML builds.

or you can use my MsBuild Helper task from the Visual Studio Market Place to configure the Output Path, then add the $(MsBuildAdditionalArguments) variable to your MsBuild or Visual Studio Build's additional arguments input:

MsBuild Helper Task enter image description here

Visual Studio Build / MsBuild Task enter image description here

jessehouwing
  • 106,458
  • 22
  • 256
  • 341
1

Also please try giving this MSBuild argument 

 /p:GenerateProjectSpecificOutputFolder=true /p:OutDirWasSpecified=true
 /p:OutputPath=$(Build.BinariesDirectory)
jessehouwing
  • 106,458
  • 22
  • 256
  • 341
Dilaksha A
  • 279
  • 3
  • 4
  • I don't think this still works in Visual Studio 2015/MsBuild 14 and up: https://social.msdn.microsoft.com/Forums/vstudio/en-US/43dcc9cf-8eff-43e2-9292-eeecd1ff3bcf/msbuild-14-generateprojectspecificoutputfolder?forum=tfsbuild – jessehouwing Sep 27 '17 at 09:11