MSBuild Improvements for main projects #49
Description
Some projects like the Files project have no reference to the main project Edi and require, therefore, copying as implemented in Edi.targets and shown below.
There is already a mechanism to mark Plugin folder projects and copy their binaries as described in the Wiki.
Question:
Should we use a similar mechanism based on a new XML Tag (eg. DeployMain instead of DeployPlugin) or is a different mechanism more appropriate?
<!-- Deploy Files toolwindow -->
<BuildDependsOn Condition="$(DeployApplication) == 'true'">
$(BuildDependsOn);
DeployFiles;
</BuildDependsOn>
<Target Name="DeployFiles">
<!-- Deploy Files assembly since its otherwise missing
because Edi's main project requires no additional reference -->
<ItemGroup>
<FilesModul Include="$(SolutionDir)\Tools\BuiltIn\Files\bin\$(Configuration)\**\*.*" />
</ItemGroup>
<Copy SourceFiles="@(FilesModul)"
DestinationFolder="$(ApplicationTargetDir)%(RecursiveDir)"
ContinueOnError="false"
SkipUnchangedFiles="false"
/>
<!-- Message Text=" %(FilesModul.Identity)" Importance="High"/-->
</Target>