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/27 15:42] – vagabond | op2_sdk:projectsettings [2016/10/06 06:39] – [Changing the file target name] vagabond | ||
---|---|---|---|
Line 1: | Line 1: | ||
====== Development Environment Project Settings ====== | ====== Development Environment Project Settings ====== | ||
- | This page lists some common development environment customizations | + | This page lists common development environment customizations when creating Outpost 2 scenario DLLs using Visual Studio. The customizations include |
Within the Outpost Universe repository, the Outpost 2 API uses the IDE Microsoft Visual Studio. These instructions are for Visual Studio, but the general principles should apply to other IDEs such as Code:: | Within the Outpost Universe repository, the Outpost 2 API uses the IDE Microsoft Visual Studio. These instructions are for Visual Studio, but the general principles should apply to other IDEs such as Code:: | ||
Line 11: | Line 11: | ||
- Open your Project in Visual Studio. | - Open your Project in Visual Studio. | ||
- In the solution explorer, right click on your project -> Properties. | - In the solution explorer, right click on your project -> Properties. | ||
- | - Click Configuration Properties -> General -> Target Name. Update the name as you see fit. | + | |
+ | - Set Platform to All Platforms. | ||
+ | | ||
{{ op2_sdk: | {{ op2_sdk: | ||
+ | |||
+ | ---- | ||
===== Copying Scenario DLL using a Post Build Event ===== | ===== Copying Scenario DLL using a Post Build Event ===== | ||
- | In order to simplify testing | + | To simplify testing a scenario DLL, consider setting a post build event to copy required files directly into the Outpost 2 root install directory. Post build events are executed every time the project is re-compiled. |
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 '' | ||
Line 26: | Line 30: | ||
- Repeat for each file you want copied to the new directory. | - Repeat for each file you want copied to the new directory. | ||
- | Note: In the copy command, the ''/ | + | 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:** //In the copy command, the ''/ | ||
+ | |||
+ | **Note:** //Paths passed as arguments into the copy command cannot contain spaces unless the path is enclosed in parenthesis. For example// ''" | ||
{{ op2_sdk: | {{ op2_sdk: | ||
+ | |||
+ | ---- | ||
===== 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. | + | Executable files can be referenced from within Visual Studio. This allows running Outpost 2 from within Visual Studio when testing a mission DLL. |
- | To add the Outpost 2 executable as an existing project to your Visual Studio Solution. | + | 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' |
+ | |||
+ | 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). | - File -> Add -> Existing Project -> Select Outpost2.exe (from wherever it is installed on your machine). | ||
Line 44: | Line 61: | ||
{{ op2_sdk: | {{ op2_sdk: | ||
+ | |||
+ | ---- | ||
===== Debugging Custom Mission DLLs ===== | ===== Debugging Custom Mission DLLs ===== | ||
Line 57: | Line 76: | ||
{{ op2_sdk: | {{ op2_sdk: | ||
- | Note: The Visual Studio must have access to your scenario' | + | **Note:** //The Visual Studio must have access to your scenario' |
---- | ---- |