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/02/29 19:55] – vagabond | op2_sdk:projectsettings [2016/03/03 19:02] – vagabond | ||
---|---|---|---|
Line 30: | Line 30: | ||
If placing a project into the Outpost2SVN, | If placing a project into the Outpost2SVN, | ||
- | * See the Outpost 2 game on the repository at Outpost2SVN/GameDownload/Trunk. | + | * See the Outpost 2 game on the repository at Outpost2SVN\GameDownload\Outpost2\Trunk. |
* For an output path example, use a path similar to '' | * 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:** //In the copy command, the ''/ | **Note:** //In the copy command, the ''/ | ||
Line 43: | Line 45: | ||
===== Referencing the Outpost 2 executable ===== | ===== Referencing the Outpost 2 executable ===== | ||
- | Executable files can be referenced from within Visual Studio. This allows running Outpost 2 from within Visual Studio when testing a mission DLL. An alternative option to referencing Outpost2.exe | + | Executable files can be referenced from within Visual Studio. This allows running Outpost 2 from within Visual Studio when testing a mission DLL. |
+ | |||
+ | An alternative option to referencing Outpost2.exe within the solution | ||
To add the Outpost 2 executable as an existing project to a Visual Studio Solution. | To add the Outpost 2 executable as an existing project to a Visual Studio Solution. |