Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revisionLast revisionBoth sides next revision | ||
op2_sdk:projectsettings [2016/02/29 19:46] – vagabond | op2_sdk:projectsettings [2016/10/12 21:32] – external edit 127.0.0.1 | ||
---|---|---|---|
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: | ||
Line 22: | 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: | ||
+ | |||
+ | * copy /Y " | ||
+ | * copy /Y " | ||
+ | * copy /Y " | ||
+ | |||
+ | **Setting Post Build Event Instructions** | ||
- In the Solution Explorer, right click on the project you wish to include a post build event and click on properties. | - In the Solution Explorer, right click on the project you wish to include a post build event and click on properties. | ||
+ | - Set Configuration to All Configurations. | ||
+ | - Set Platform to All Platforms. | ||
- Click Configuration Properties -> Build Events -> Post-Build Event. | - Click Configuration Properties -> Build Events -> Post-Build Event. | ||
- 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 | + | |
+ | **Note:** //Before committing | ||
**Note:** //In the copy command, the ''/ | **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 " | + | **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: | ||
Line 39: | Line 54: | ||
===== 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 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). | - File -> Add -> Existing Project -> Select Outpost2.exe (from wherever it is installed on your machine). | ||
Line 66: | 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' |
---- | ---- | ||
- //Go Back to [[op2_sdk: | - //Go Back to [[op2_sdk: | ||
- //Go Back to [[outpost_2: | - //Go Back to [[outpost_2: | ||
- | - //Go Back to [[http:// | + | - //Go Back to [[http:// |