Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

MSBuild Improvements for main projects #49

Open
Dirkster99 opened this issue Nov 9, 2018 · 0 comments
Open

MSBuild Improvements for main projects #49

Dirkster99 opened this issue Nov 9, 2018 · 0 comments

Comments

@Dirkster99
Copy link
Owner

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>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant