Skip to content

ci: build on different .NET versions (6.0, 7.0, 8.0) #43

ci: build on different .NET versions (6.0, 7.0, 8.0)

ci: build on different .NET versions (6.0, 7.0, 8.0) #43

Workflow file for this run

name: MSBuild on Windows
on: [push]
env:
# Path to the solution file relative to the root of the project.
SOLUTION_FILE_PATH: mouse-click-simulator.sln
# Configuration type to build.
# You can convert this to a build matrix if you need coverage of multiple configuration types.
# https://docs.github.com/actions/learn-github-actions/managing-complex-workflows#using-a-build-matrix
BUILD_CONFIGURATION: Release
jobs:
build:
strategy:
matrix:
dotnet:
- 6.0.x
- 7.0.x
- 8.0.x
runs-on: windows-2022
steps:
- name: Code checkout
uses: actions/checkout@v4
- name: Install .NET
uses: actions/setup-dotnet@v4
with:
dotnet-version: ${{ matrix.dotnet }}
- name: Add MSBuild to PATH
uses: microsoft/setup-msbuild@v1
- name: Restore NuGet packages
working-directory: ${{env.GITHUB_WORKSPACE}}
run: nuget restore ${{env.SOLUTION_FILE_PATH}}
- name: Build
working-directory: ${{env.GITHUB_WORKSPACE}}
# Add additional options to the MSBuild command line here (like platform or verbosity level).
# See https://docs.microsoft.com/visualstudio/msbuild/msbuild-command-line-reference
run: msbuild /m /p:Configuration=${{env.BUILD_CONFIGURATION}} ${{env.SOLUTION_FILE_PATH}}
# Inno Setup 6.2.2 is already installed on the Windows 2022 image. See
# <https://github.com/actions/runner-images/blob/main/images/windows/Windows2022-Readme.md>
# for pre-installed software.
- name: Create installer
working-directory: ${{env.GITHUB_WORKSPACE}}
# Running custom commands / executables is unnecessarily complicated in
# PowerShell, so I guess we have to do it that way.
run: |
$command = '"C:\Program Files (x86)\Inno Setup 6\iscc.exe" "setup\setup.iss"'
Invoke-Expression "& $command"
- name: Upload artifact
uses: actions/upload-artifact@v3
with:
name: installer-dotnet-${{ matrix.dotnet }}
path: output\*.exe