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:projectcreation [2021/03/06 21:12] – [Download the Outpost 2 SDK from the Outpost Repository] vagabond | op2_sdk:projectcreation [2021/03/06 21:19] – [Create a New Project through SVN Copy] vagabond | ||
---|---|---|---|
Line 16: | Line 16: | ||
First, you will need a copy of the Outpost 2 SDK. The most up to date version of the Outpost 2 SDK is stored on the Outpost Universe GitHub page. Example scenarios and templates may also be found on GitHub. To download the SDK and other example projects, see the [[opu: | First, you will need a copy of the Outpost 2 SDK. The most up to date version of the Outpost 2 SDK is stored on the Outpost Universe GitHub page. Example scenarios and templates may also be found on GitHub. To download the SDK and other example projects, see the [[opu: | ||
- | |||
- | If interested in accessing Redmine, see the [[opu: | ||
===== 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. | ||
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. |