feat: Update build copy task to use multiple paths#69
Conversation
| </ItemGroup> | ||
|
|
||
| <Copy SourceFiles="@(Binaries)" DestinationFolder="$(SilksongFolder)/BepInEx/plugins/$(TargetName)"/> | ||
| <Copy SourceFiles="@(Binaries)" DestinationFolder="%(SilksongFolders.Identity)"/> |
There was a problem hiding this comment.
This means that the property name SilksongFolder from SilksongPath.props is no longer accurate right? Because we copy directory to its path rather than the subfolders /BepInEx/plugins/SSMP?
There was a problem hiding this comment.
Yeah it's directly deploying to the specified path.
There was a problem hiding this comment.
It should probably be renamed then for clarity.
Also, what is the new syntax for defining multiple output paths?
There was a problem hiding this comment.
It will rename it but probably tomorrow.
Also, what is the new syntax for defining multiple output paths?
You need to have SilksongPath.props with this piece of metadata:
The path seperator is the ; character.
<Project>
<PropertyGroup>
<SilksongFolder>
D:\Games\Hollow Knight - Silksong\BepInEx\plugins;
D:\SteamLibrary\steamapps\common\Hollow Knight Silksong\BepInEx\plugins\SSMP
</SilksongFolder>
</PropertyGroup>
</Project>
Extremelyd1
left a comment
There was a problem hiding this comment.
I didn't entirely agree with the way you've added items and properties, so I've reworked the configuration to what I think is the most straightforward and maintainable.
This way you can define multiple output directories by defining multiple OutputDirectory tags in the LocalBuildProperties.props file.
No description provided.