Why doesn't MSBuild copy as I would expect

Question

I\'m needing to script my build. I\'m using MSBUILD because of it\'s integration with VS.net. I am trying to copy some files from the build environment to the deployment folder

Answer 1

I found the example in one of the examples in MSDN I don't understand it but will leave an example for my fellow travlers here in stackoverflow. Here is the fixed version of the migrate target from above:

<Target Name="migrate" DependsOnTargets="Clean">
    <Copy DestinationFiles="@(SourceDir->'$(DeployPath)\%(RecursiveDir)%(Filename)%(Extension)')" SourceFiles="@(SourceDir)" />
</Target>

If someone actually understands this example please explain. Good Luck!

Answer 2

When you specify the DestinationFolder for the Copy task, it takes all items from the SourceFiles collection and copies them to the DestinationFolder. This is expected, as there is no way for the Copy task to figure out what part of each item's path needs to be replaced with the DestinationFolder in order to keep the tree structure. For example, if your SourceDir collection is defined like this:

<ItemGroup>
    <SourceDir Include="$(Source)\**\*" />
    <SourceDir Include="E:\ExternalDependencies\**\*" />
    <SourceDir Include="\\sharedlibraries\gdiplus\*.h" />
</ItemGroup>

What would you expect the destination folder tree look like?

To preserve the tree, you need to do identity transformation and generate one destination item for each item in the SourceFiles collection. Here's an example:

<Copy SourceFiles="@(Compile)" DestinationFiles="@(Compile->'$(DropPath)%(Identity)')" />

The Copy task will take the each item in the SourceFiles collection, and will transform its path by replacing the part before the ** in the source item specification with $(DropPath).

One could argue that the DestinationFolder property should have been written as a shortcut to the following transformation:

<Copy SourceFiles="@(Compile)" DestinationFiles="@(Compile->'$(DestinationFolder)%(Identity)')" />

Alas, that would prevent the deep copy to flat folder scenario that you are trying to avoid, but other people might using in their build process.

Answer 3

Just a gem we found as we were debugging MSBuild issues around copying:

http://blog.scrappydog.com/2008/06/subtle-msbuild-bug-feature.html

ItemGroups are parsed before Targets, so any Targets that create new files (e.g. compiles!) won't be picked up when an ItemGroup is referenced further along the script.

Eric Bowen also describes a work-around for this "feature", the CreateItem task:

<Target Name="Copy" >
    <CreateItem Include="..\Source\**\bin\**\*.exe"
        Exclude="..\Source\**\bin\**\*.vshost.exe">
        <Output TaskParameter="Include" ItemName="CompileOutput" />
    </CreateItem>
    <Copy SourceFiles="@(CompileOutput)" 
        DestinationFolder="$(OutputDirectory)"></Copy>
</Target>

Many kudos to him!

Answer 4

Very simple example that copies a directory contents and structure recursively:

<Copy SourceFiles="@(Compile)" DestinationFolder="c:\foocopy\%(Compile.RecursiveDir)"></Copy>

@(Compile) is an ItemGroup of all files that you want to copy. Could be something like:

   <ItemGroup>
      <Compile Include=".\**\*.dll" /> 
   </ItemGroup>

The Copy task will copy all the files into c:\foocopy just like xcopy.