Differences

This shows you the differences between two versions of the page.

--- op2_sdk:projectsettings [2016/02/27 16:24] – vagabond
+++ op2_sdk:projectsettings [2016/03/01 19:22] – vagabond
@@ Line 27: / Line 27: @@
   - Set the Command Line to perform a copy event.
   - Repeat for each file you want copied to the new directory.
+If placing a project into the Outpost2SVN, copy your output files into the repository's Outpost 2 game folder using a relative path. This allows post build events to work on other computers where the repository is downloaded without changing the destination of post build event copies.
+  * See the Outpost 2 game on the repository at Outpost2SVN\GameDownload\Outpost2\Trunk.
+  * For an output path example, use a path similar to ''..\..\..\..\GameDownload\Outpost2\trunk\''.
 **Note:** //In the copy command, the ''/Y'' instructs the copy command to overwrite existing files. Place the original file first and the location you want the file copied to second.//
+**Note:** //Paths passed as arguments into the copy command cannot contain spaces unless the path is enclosed in parenthesis. For example// ''"C:/Outpost 2"'' //is valid while// ''C:/Outpost 2'' //is not valid.//
 {{ op2_sdk:projectsettings:post_build_copy_visual_studio_2015.png }}
@@ Line 36: / Line 43: @@
 ===== 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 within the solution is to set Outpost2.exe as the startup executable for the scenario DLL. To do this, set Outpost 2 as the external executable under the DLL project's debug settings.
-To add the Outpost 2 executable as an existing project to your Visual Studio Solution.
+To add the Outpost 2 executable as an existing project to a Visual Studio Solution.
   - File -> Add -> Existing Project -> Select Outpost2.exe (from wherever it is installed on your machine).