Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • Home
  • SEARCH
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 3213736
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 17, 20262026-05-17T14:58:44+00:00 2026-05-17T14:58:44+00:00

I’m trying to "fix" a build on our TF Server that drops everything into

  • 0

I’m trying to "fix" a build on our TF Server that drops everything into the drop folder in one big flat drop (rather than in seperate project dumps like a local build would do), and I’m getting a little frustrated – I’m going to be honest and say this is the first time I’ve ever worked with MSBuild and this has kind of been droppped on me – it’s not a build file I configured from scratch.

I’ve found a bunch of solutions online, and most point to this blog, which looks good. Unfortunately it doesn’t seem to solve my problems at all.

In TFSBuild.proj I have a lump of code that looks like:

<SolutionToBuild Include="$(BuildProjectFolderPath)/../../mySolution.sln">
 <Targets>SomeProject\Project</Targets>
  <Properties>
    CustomizableOutDir=true;
  </Properties>
</SolutionToBuild>

And as far as I can tell from that CustomizableOutDir is indeed set to true which should allegedly retain directory structure. I tried editing some of the project files as indicated in the blog, like so…

<Target Name="AfterCompile" Condition="'$(TeamBuildOutDir)' != ''">
    <ItemGroup>
       <CompileOutputs Include="$(OutDir)\**\*" />
    </ItemGroup>
    <Copy 
      SourceFiles="@(CompileOutputs)"
      DestinationFolder=
      "$(TeamBuildOutDir)\ProjectName\%(RecursiveDir)" />
</Target>

But that behaves weirdly – if I edit several project files I begin to get what looks like I might be approaching a correct solution, but still isn’t good enough – I get a directory structure that contains folders like MyProj1 and MyProj2, yet MyProj2 seems to of had all the output from MyProj1 dumped into it (MyProj1 works as I’d hope it to). On top of this the drop folder still has everything else dumped in one big drop (the directories contain duplicates of this drop).

Does anyone have any idea of what could be causing CustomizableOutDir to not behave as expected? Or is there a problem with my csproj file code?

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-17T14:58:44+00:00Added an answer on May 17, 2026 at 2:58 pm

    I’ve seen several suggestions about how to pass the CustomizableOutDir property to msbuild for a solution.

    1. As you has provided in the question, add <Properties>CustomizableOutDir=true</Properties> for the SolutionToBuild Item. (What’s the best way to get TFS to output each project to its own directory?)
    2. Add <CustomizableOutDir>true</CustomizableOutDir> to the main PropertyGroup (TFS Build 2008 – Custom output directories)
    3. Add /p:CustomizableOutDir=true to TFSBuild.rsp (TFS Build 2008 – Custom output directories)

    I’ve tried all three approaches and the last option (TFSBuild.rsp command line option) was the only one I could get working. I combined this with conditions on each OutputPath in the csproj files rather than a AfterCompile Target. E.g.

    <PropertyGroup Condition=" '$(Configuration)|$(Platform)' == 'Debug|AnyCPU' ">
        <OutputPath Condition=" '$(TeamBuildOutDir)'=='' ">bin\debug\</OutputPath>
        <OutputPath Condition=" '$(TeamBuildOUtDir)'!='' ">$(TeamBuildOutDir)projectName</OutputPath>
    </PropertyGroup> 
    
    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

No related questions found

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.