Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Next revisionBoth sides next revision | ||
op2_sdk:projectsettings [2016/10/06 06:51] – [Copying Scenario DLL using a Post Build Event] vagabond | op2_sdk:projectsettings [2016/10/06 08:44] – [Debugging Custom Mission DLLs] vagabond | ||
---|---|---|---|
Line 24: | Line 24: | ||
Visual Studio uses macros in pre and post build events to simplify commands. For example '' | Visual Studio uses macros in pre and post build events to simplify commands. For example '' | ||
+ | |||
+ | A vanilla copy of the current Outpost 2 release is kept in the repository at '' | ||
**Example Post Build copy commands: | **Example Post Build copy commands: | ||
Line 39: | Line 41: | ||
- Set the Command Line to perform a copy event. | - Set the Command Line to perform a copy event. | ||
- Repeat for each file you want copied to the new directory. | - Repeat for each file you want copied to the new directory. | ||
- | |||
- | If placing a project into the Outpost2SVN, | ||
- | |||
- | * See the Outpost 2 game on the repository at Outpost2SVN\GameDownload\Outpost2\Trunk. | ||
- | * For an output path example, use a path similar to '' | ||
**Note:** //Before committing a new project to the repository, turn the post build events into remarks by prefixing them with the rem keyword. This prevents the post build events from executing unless the user downloading your source code explicitly wants them.// | **Note:** //Before committing a new project to the repository, turn the post build events into remarks by prefixing them with the rem keyword. This prevents the post build events from executing unless the user downloading your source code explicitly wants them.// | ||
Line 86: | Line 83: | ||
{{ op2_sdk: | {{ op2_sdk: | ||
- | **Note:** //The Visual Studio must have access to your scenario' | + | **Note:** //Visual Studio must have access to your scenario' |
---- | ---- |