added Azure Pipelines build system (#88)

build-system/README.md

@@ -0,0 +1,6 @@
+# Azure Pipelines Build Files
+These `.yaml` files are used by Windows Azure DevOps Pipelines to help execute the following types of builds:
+
+- Pull request validation on Linux (Mono / .NET Core)
+- Pull request validation on Windows (.NET Framework / .NET Core)
+- NuGet releases with automatic release notes posted to a Github Release repository.

build-system/linux-pr-validation.yaml

@@ -0,0 +1,25 @@
+# Pull request validation for Linux against the `dev` and `master` branches
+# See https://docs.microsoft.com/en-us/azure/devops/pipelines/yaml-schema for reference
+
+pool:
+  vmImage: Hosted Ubuntu 1604
+
+variables:
+
+pr:
+  autoCancel: boolean # indicates whether additional pushes to a PR should cancel in-progress runs for the same PR. Defaults to true
+  branches:
+    include: [ dev, master ] # branch names which will trigger a build
+
+steps:
+- checkout: self  # self represents the repo where the initial Pipelines YAML file was found
+  clean: false  # whether to fetch clean each time
+  submodules: recursive  # set to 'true' for a single level of submodules or 'recursive' to get submodules of submodules
+  persistCredentials: true
+
+- task: Bash@3
+  displayName: 'FAKE Build'
+  inputs:
+    targetType: ./
+    filePath: build.sh
+    arguments: all

build-system/windows-pr-validation.yaml

@@ -0,0 +1,25 @@
+# Pull request validation for Windows against the `dev` and `master` branches
+# See https://docs.microsoft.com/en-us/azure/devops/pipelines/yaml-schema for reference
+
+pool:
+  vmImage: Hosted VS2017
+  demands: Cmd
+
+variables:
+
+pr:
+  autoCancel: boolean # indicates whether additional pushes to a PR should cancel in-progress runs for the same PR. Defaults to true
+  branches:
+    include: [ dev, master ] # branch names which will trigger a build
+
+steps:
+- checkout: self  # self represents the repo where the initial Pipelines YAML file was found
+  clean: false  # whether to fetch clean each time
+  submodules: recursive  # set to 'true' for a single level of submodules or 'recursive' to get submodules of submodules
+  persistCredentials: true
+
+- task: BatchScript@1
+  displayName: 'Run script build.cmd'
+  inputs:
+    filename: build.cmd
+    arguments: all

build-system/windows-release.yaml

@@ -0,0 +1,28 @@
+# Release task for PbLib projects
+# See https://docs.microsoft.com/en-us/azure/devops/pipelines/yaml-schema for reference
+
+pool:
+  vmImage: Hosted VS2017
+  demands: Cmd
+
+variables:
+  - group: signingSecrets
+  - group: nugetKeys
+  - group: githubData
+
+steps:
+- task: BatchScript@1
+  displayName: 'FAKE Build'
+  inputs:
+    filename: build.cmd
+    arguments: 'All SignClientUser=$(signingUsername) SignClientSecret=$(signingPassword) nugetpublishurl=https://www.nuget.org/api/v2/package nugetkey=$(nugetKey)'
+
+- task: GitHubRelease@0
+  displayName: 'GitHub release (create)'
+  inputs:
+    gitHubConnection: $(githubConnectionName)
+    repositoryName: $(githubRepositoryName)
+    title: '$(projectName) v$(Build.SourceBranchName)'
+    releaseNotesFile: 'RELEASE_NOTES.md'
+    assets: |
+     bin\nuget\*.nupkg