Skip to content

Document how to automate copying dlls, sources and configs from FFWD #12

Description

@Elideb

Every time I've merged the latest FFWD changes into my version of the project and template I've ran into issues because I'd forget copying some dll, config or whatever. Once those were fixed manually I had many problems because Visual Studio cached lots of compiled stuff from previous versions. It would require lots of cleaning, recompiling and exporting for things to work again, to the point that recreating the scenes in a new project was usually easier.

In the end I have created my base project from scratch, based on this one, automating all operations with the AfterBuild bats. It'd be great if there were some documentation about why and how to use those files (the samples are not mentioned in the Getting Started page). Updating the samples to be more complete would be great too.

For example, my Exporter.AfterBuild.bat looks like this:

REM Copy Exporter dll to Unity
copy %1                                     %2\..\..\Unity\Assets\Editor\FFWD\
copy %1.config                                  %2\..\..\Unity\Assets\Editor\FFWD\

And Unity.AfterBuild.bat:

REM Copy FFWD.Unity editor scripts to Unity
REM Copy ExportSceneWizard.config?
copy %2\PressPlay.FFWD.Unity\Editor\*.cs    %2\..\..\Unity\Assets\Editor\FFWD\
REM Copy FFWD.Unity sources to Unity FFWD
copy %2\PressPlay.FFWD.Unity\*.cs           %2\..\..\Unity\Assets\FFWD\

Both of them receive the same parameters, "$(TargetPath)" "$(SolutionDir)", just in case.

With these changes I'm now able to merge and change FFWD sources without all the head banging it previously required. I think making this bat files feature more prominently on the wiki would make things easier for other users.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions