beasty/csp-app-multiplexer
1
0
Fork 0
Code Issues Pull requests Releases 1 Wiki Activity Actions
Page: Build from Source
Pages
Build from Source Connection Scope Home How It Works Installation Palette Companion Integration
1 Build from Source
publish-wiki edited this page 2026-07-27 13:11:45 +02:00
Table of Contents

Build from source

Windows only. WPF cannot be built on Linux or macOS at all — the Windows Desktop SDK is not available there. The Protocol and Broker libraries are plain net8.0 and do build anywhere; only the app does not.

Need Version
.NET SDK 8.0
OS Windows 10/11 64-bit 
dotnet build CspAppMultiplexer.sln -c Release
dotnet test  CspAppMultiplexer.sln -c Release --no-build

TreatWarningsAsErrors is on. A warning fails the build.

Release artifacts

tools\publish-local.ps1 -Version 1.0.0

Writes to dist\release\ with SHA256SUMS.txt. Same flags as CI, so a hand-cut release and a tagged one produce identical files.

Artifact Size Flags
…-needs-dotnet8.exe 2.3 MiB --self-contained false -p:PublishSingleFile=true
…-standalone.exe 68.7 MiB --self-contained true -p:PublishSingleFile=true -p:EnableCompressionInSingleFile=true -p:IncludeAllContentForSelfExtract=true

IncludeAllContentForSelfExtract is load-bearing. Without it the publish leaves five native WPF DLLs (D3DCompiler_47_cor3, wpfgfx_cor3, PresentationNative_cor3, PenImc_cor3, vcruntime140_cor3) loose beside the exe, so the "standalone" download does not run on its own.

Trimming and NativeAOT are not possible here. -p:PublishTrimmed=true fails with NETSDK1175: the app references WinForms, for the tray icon and for ZXing. Do not add either flag.

Versioning

Directory.Build.props defaults to 0.1.0; a v* tag drives the real version through -p:Version=. The app csproj carries no <Version> — a project-level value silently wins over the command line.

Theme.xaml

src\CspMultiplexer.App\Theme\Theme.xaml is byte-identical to the copy in the CSP Palette Companion repository. A SuiteSyncCheck build target fails on drift; tools\suite-sync.ps1 -Mode Push reconciles the two working trees when both are checked out side by side.

CI

.forgejo/workflows/ci.yml splits on the only line that matters:

Job Runner Covers
libraries Linux Protocol, Broker and their tests, by explicit project list
windows Windows the WPF app, all tests, every release artifact

The Linux job never touches the .sln — that would pull in the WPF app and fail. It also checks out with git rather than an action, because the .NET SDK container ships no Node.js and every checkout action is a node20 JavaScript action.

release.yml runs on a v* tag and calls publish-local.ps1, then creates the release through the Forgejo API with curl. Auth header is token, not Bearer.