skills.rest
ArMaTeC
ArMaTeCCOMMUNITY
Explore all skills by this author →
GitHub

redball-deployment-guide

Guides building, signing, and deploying the Redball WPF application on Windows.

Updated Mar 9, 2026
Search Tags:#ci/cd#deployment#dotnet#wpf#windows#code signing#nsis
One-click install
npx skills add https://github.com/ArMaTeC/Redball --skill redball-deployment-guide-armatec
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: redball-deployment-guide
Source: https://github.com/ArMaTeC/Redball
Command: npx skills add https://github.com/ArMaTeC/Redball --skill redball-deployment-guide-armatec

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Deploying a .NET 10 WPF desktop application involves coordinating builds, tests, NSIS installer creation, code signing, and CI/CD releases, and missing a step produces broken or unsigned artifacts. ## Core Features & Use Cases - Pre-deployment Checklist: Verifies Windows version, .NET 10 SDK, NSIS, signing certificates, and GitHub secrets before release. - Three Deployment Methods: NSIS installer via build.ps1, self-contained single-file EXE via dotnet publish, and a development setup workflow. - Code Signing & CI/CD: Covers signtool usage, GitHub Actions secrets, and the ci.yml, release.yml, and virustotal.yml workflows. - Use Case: A maintainer preparing Redball v2.1.655 for release runs the checklist, bumps the version with Bump-Version.ps1, executes the full signed build pipeline, and publishes a GitHub Release with the branded installer. ## Quick Start Ask the assistant to walk you through building and signing a Redball release installer using the build script and code signing certificate.

Frequently Asked Questions about redball-deployment-guide

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I build a signed NSIS installer for a WPF application?▼

Run the build.ps1 script with the 'all' target to build the WPF app, create the NSIS installer, and sign both artifacts. Signing requires a PFX certificate and password configured locally or as GitHub secrets for CI.

How do I publish a self-contained single-file .NET 10 EXE?▼

Use dotnet publish with --self-contained true, -r win-x64, -p:PublishSingleFile=true, and -p:EnableCompressionInSingleFile=true. This produces a single compressed EXE of roughly 3.3MB with the runtime embedded.

What GitHub secrets are needed for automated code signing?▼

The release workflow requires CODE_SIGNING_CERT, a base64-encoded PFX certificate, and CODE_SIGNING_PASSWORD. The release.yml workflow uses these with signtool.exe to sign the EXE and installer automatically.

Does the Redball installer require administrator rights?▼

No, the NSIS installer performs a per-user installation to %LocalAppData%\Redball without requiring admin privileges. It creates Start Menu, Desktop, and optional startup shortcuts.

Why does the Redball build fail with NSIS not found?▼

The build script requires NSIS v3.0 or later installed on the machine to generate the installer. Download it from nsis.sourceforge.io or install it via a package manager, then rerun the build.

Related Skills

Explore More Software Engineering Skills→
githubgithub
37.6k

winapp-cli

Initialize Windows app projects, generate manifests, and package MSIX files.

Official
Advanced
pedronauckpedronauck
567

electron-builder

Automate packaging, code signing, notarization, and distribution of Electron apps.

Community
Advanced
jmylchreestjmylchreest
15

verify

Run tests, type checks, linting, and builds across TypeScript, Go, and Python.

Community
Advanced
GongXLiangGongXLiang

build-mcpb

Bundle a local MCP server with its runtime into a portable MCPB package.

Community
Advanced