Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
op2_sdk:projectsettings [2016/03/01 19:22] – vagabond | op2_sdk:projectsettings [2016/11/03 17:40] (current) – Moved Debuging Scenario information to a separate wiki page. vagabond | ||
---|---|---|---|
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 |
- | + | ||
- | * See the Outpost 2 game on the repository at Outpost2SVN\GameDownload\Outpost2\Trunk. | + | |
- | * For an output path example, use a path similar to '' | + | |
**Note:** //In the copy command, the ''/ | **Note:** //In the copy command, the ''/ | ||
Line 59: | Line 70: | ||
---- | ---- | ||
- | + | - //Go Back to [[op2_sdk: | |
- | ===== Debugging Custom Mission DLLs ===== | + | |
- | + | ||
- | Since we do not have access to the Outpost 2 source code or program debug database (PDB file), we cannot step through the Outpost 2 executable code or compare the stack trace with source code. However, we can still debug custom scenario DLLs. | + | |
- | + | ||
- | In order to debug your DLL, follow the required steps from previous sections to ensure a copy of all required files (mission DLL, MAP file, tech tree file, etc) are contained in the Outpost 2 root directory. Then ensure your Visual Studio project is linked to Outpost 2. | + | |
- | + | ||
- | - Recompile your project if needed. | + | |
- | - Set a break point where you want to examine the code or perform whatever other debugging action. | + | |
- | - Press Start Debugging (or hit F5). Outpost 2 should load normally. Once Outpost 2 accesses your DLL, Visual Studio should pause the program at the break point and let you examine the stack trace. | + | |
- | + | ||
- | {{ op2_sdk: | + | |
- | + | ||
- | **Note:** //The Visual Studio must have access to your scenario' | + | |
- | + | ||
- | ---- | + | |
- | - //Go Back to [[op2_sdk: | + | |
- //Go Back to [[outpost_2: | - //Go Back to [[outpost_2: | ||
- | - //Go Back to [[http:// | + | - //Go Back to [[http:// |