Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
op2_sdk:projectcreation [2016/11/03 17:52] – [Further Project Settings] vagabond | op2_sdk:projectcreation [2021/03/06 21:25] (current) – [Download the Outpost 2 SDK from the Outpost Repository] vagabond | ||
---|---|---|---|
Line 13: | Line 13: | ||
Once you have an IDE project compiling DLLs for Outpost 2, review the [[op2_sdk: | Once you have an IDE project compiling DLLs for Outpost 2, review the [[op2_sdk: | ||
- | ===== Download | + | ===== Pull the Outpost 2 SDK from the Outpost Repository ===== |
- | First, you will need a copy of the Outpost 2 SDK. The most up to date version of the Outpost 2 SDK is stored | + | First, you will need a copy of the Outpost 2 SDK. The most up to date version of the Outpost 2 SDK is stored |
- | + | ||
- | A scenario | + | |
===== Create a New Project through SVN Copy ===== | ===== Create a New Project through SVN Copy ===== | ||
- | |||
- | The recommended way to start a new Outpost 2 scenario is by using Subversion (SVN) copy to create a copy of an existing template. Starting templates of scenarios can be found on the repository at [[https:// | ||
The benefits of using SVN copy is that a link between the original template and the new scenario is maintained in the repository. The majority (if not all) the project and solution properties will already be preset to the correct values. SVN copy will also be faster then creating a new blank project and setting all the values manually. | The benefits of using SVN copy is that a link between the original template and the new scenario is maintained in the repository. The majority (if not all) the project and solution properties will already be preset to the correct values. SVN copy will also be faster then creating a new blank project and setting all the values manually. |