The included build target script flattens the directory structure of content files.
__Example content files__ (Build Action: Content; Copy if newer):
* \Command\luatest.lua
* \ModInfo.xml
__Extract of the build log:__
```
1>Done executing task "MSBuild.ILMerge.Task".
2>Using "Copy" task from assembly "Microsoft.Build.Tasks.Core, Version=15.1.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a".
3>Task "Copy"
4> Copying file from "ModInfo.xml" to "bin\Debug\ModInfo.xml".
5> Copying file from "Commands\luatest.lua" to "bin\Debug\luatest.lua".
6>Done executing task "Copy".
```
See line 5: "luatest.lua" is losing it's directory "Commands".
Given that projects often contain a LOT of deeply structured content files and folders (e.g. html, css, images, js, ...), this makes the build task unusable for such projects.
__Reason:__
The Copy task does not keep directory structure if used like this.
```
<Copy SourceFiles="@(LocalContentFiles)" DestinationFolder="$(OutputPath)" />
```
__Suggested Fix:__
The documentation of the Copy task contains an example at the end on how to use it to keep directory structure intact. Adjust the target file accordingly:
```
The following example demonstrates how to do a recursive copy.
This project copies all of the files recursively from c:\MySourceTree
into c:\MyDestinationTree, while maintaining the directory structure.
<Project xmlns="http://schemas.microsoft.com/developer/msbuild/2003">
<ItemGroup>
<MySourceFiles Include="c:\MySourceTree\**\*.*"/>
</ItemGroup>
<Target Name="CopyFiles">
<Copy
SourceFiles="@(MySourceFiles)"
DestinationFiles="@(MySourceFiles->'c:\MyDestinationTree\%(RecursiveDir)%(Filename)%(Extension)')"
/>
</Target>
</Project>
```
https://msdn.microsoft.com/en-us/library/3e54c37h.aspx
Comments: Correction for the suggested fix. This is what worked for me in the end:
```
<Copy SourceFiles="@(LocalContentFiles)" DestinationFiles="@(LocalContentFiles->'$(OutputPath)%(Identity)')" />
```