Set up CI with Azure Pipelines

azure-pipelines.yml

@@ -0,0 +1,22 @@
+trigger:
+- master
+
+pr:
+- master
+
+jobs:
+- job: Build
+
+  pool:
+    vmImage: 'ubuntu-latest'
+
+  variables:
+    buildConfiguration: 'Release'
+
+  steps:
+  - script: dotnet run --configuration $(buildConfiguration) --project src/Core/BuildTools/BuildTools.csproj build/binder_scripts/build.json
+    displayName: 'Bind'
+  - script: dotnet pack --configuration $(buildConfiguration) --version-suffix build$(Build.BuildNumber)
+    displayName: 'Build/Pack'
+  - publish: build/output_packages
+    artifact: NuGet Packages

build/props/common.props

@@ -3,7 +3,8 @@
         <PackageIconUrl>https://static.ultz.co.uk/img/SilkDotNet.png</PackageIconUrl>
         <PackageLicenseExpression>MIT</PackageLicenseExpression>
         <PackageReleaseNotes>- First preview release</PackageReleaseNotes>
+        <PackageOutputPath>$(MSBuildThisFileDirectory)/../output_packages</PackageOutputPath>
         <Version>1.0.0-preview</Version>
         <Description>Silk.NET is a high-speed, advanced library, providing bindings to popular low-level APIs such as OpenGL and OpenAL.</Description>
     </PropertyGroup>
-</Project>
+</Project>

src/Windowing/Silk.NET.Windowing.Desktop/GlfwWindow.cs

@@ -420,7 +420,7 @@ public unsafe void Run()
                 }
                 else {
                     // Raise UpdateFrame, but don't await it yet.
-                    var task = Task.Run(RaiseUpdateFrame);
+                    var task = Task.Run((Action)RaiseUpdateFrame); // cast to action, ambiguous call
 
                     // Loop while we're still updating - the Update thread might be calling the main thread
                     while (!task.IsCompleted)