-
Notifications
You must be signed in to change notification settings - Fork 4
How Do I use It (Workflow)
JieGou edited this page Mar 27, 2020
·
2 revisions
- create your original project. You probably already did this.
- decide you want to build a different version of it
- create a solution folder in the root called
_Builds. I do this so it's at the top of the Solution Explorer and easy to find. Also, it's out of the way of the main project. - Run the GUI app, create the destination Project.
- drop CodeLinker.exe in the Solution root. It's not massive so don't panic.
- run CodeLinker.exe
- add references and fix things in your destination Project.
- carry on with your original project
- rinse & repeat
- decide on a strategy for keeping the destination Projects up-to-date by...
- Visual Studio Project post-build process, add the command line(s) with args to your source project's
Build Eventstab in theProject Propertieswindow, in thePost-build event command line:text box. If you add it to the source project it updates its destinations whenever you build it. The targets don't have to be loaded in Visual Studio, actually life is (sometimes) easier if they aren't because VS will want to reload them if/when they change. - Set up a
.cmdor.batwith a command line or few and run it when you think it all needs a refresh.
Diff all the things after a recycle to make sure I haven't eaten a kitten by mistake.