Build

Development Environment

The CDP4 Services are developed using Visual Studio 2017. At the time of writing the team is using version 15.7.6. The CDP4 Webservices contain multiple projects that target multiple .NET Frameworks, the CDP4WebServer targets net472. net472 is not yet a part of Visual Studio, the .NET Framework 4.7.2 Developer pack needs to be downloaded from the Microsoft website and installed. It is listed here, or can be downloaded directly from here.

It may be that the .NET Framework 4.7.1 Developer pack needs to be seperately installed as well.

The following tools are used by the RHEA development team:

• Visual Studio 2017 Professional (Community Edtion will work as well)
• Resharper Ultimate 2018.1.3 or later
• Git Extensions
• Docker

Build

The CDP4 Web Services solution contains three build configurations:

• test: used to test agains the Integration Test Suite on the test database docker container
• debug: used while developing new features
• release: used to create a build for release

Release

In order to create a new release of the CDP4 Web Services the following steps need to be taken.

1. Make sure the version numbers are incremented when components have changed; the project makes use of SEMVER. The version of the CDP4WebServer project shall be equal or higher than the highest version of any of it's project dependencies.
2. Verify correctness of fixes using the test build configuration and the Integration Test Suite
3. Build the solution in release mode
4. Archive the contents of the CDP4-WebServices-Community-Edition\CDP4WebServer\bin\Release\net472 folder using ZIP and name the zip file: CDP4WebServices-MAJOR.MINOR.PATCH.zip, according to SEMVER and the versioning scheme explained above.
5. Create a tag (MAJOR.MINOR.PATCH) on the Git repository and push this to GitHub. The tag shall be the version number according to SEMVER and the versioning scheme explained above.
6. Via the GitHub web-ui draft a new release referencing the tag and set the release title to Version MAJOR.MINOR.PATCH. The description of the release shall mention the updates referencing the GitHub issue numbers.
7. Upload the ZIP archive to the drafted release
8. Save the new release