Technical overviewWindows tooling and release automation

Winget App Installer

A transparent machine-setup tool built on official package sources.

Role
Solo developer across PowerShell, WinForms, package orchestration, release packaging, and documentation
Evidence status
v1.0.1 release workflow verified and executable published on GitHub
Verified
2026-07-23

01

Purpose and scope

Winget App Installer is a searchable Windows desktop utility for selecting common applications and installing them silently through winget. The repository also provides editable Windows and Linux scripts, while GitHub Actions compiles and publishes the Windows executable from version tags.

What it is used for

  • Bootstrap a new Windows machine by installing a chosen set of common applications.
  • Review or customize the package catalogue before anything is installed.
  • Reuse editable command-line scripts for Windows or major Linux package managers.
  • PowerShell
  • WinForms
  • Winget
  • Shell
  • GitHub Actions
  • ps2exe

02

Architecture

Desktop interaction

User interface

WinForms interface

Search, categories, checkboxes, progress, and live log

Configuration

Application catalogue

Readable display names mapped to exact winget IDs

Selected package IDs

Local orchestration

Application logic

PowerShell coordinator

Validates winget, disables controls, and runs installs

Feedback

Progress and logging

Maps command output and exit codes to user feedback

winget install

Package infrastructure

System package manager

Winget client

Exact, silent, non-interactive install commands

External source

Configured sources

Resolve official package manifests and installers

Output

Installed applications

Machine state after successful package operations

Distributed through

Release engineering

Trigger

Version tag

Starts the automated release workflow

CI pipeline

GitHub Actions + ps2exe

Compiles the script on a clean Windows runner

Distribution

GitHub Release

Publishes AppInstaller.exe as the release asset

Text equivalent: On the user's Windows machine, a WinForms interface maps selected applications to exact package IDs. A PowerShell coordinator invokes winget, streams output into the log, and updates progress from each exit code. Separately, tagged commits trigger GitHub Actions to compile and publish the executable.

03

Engineering decisions

Use the operating system package manager

Winget resolves packages from its configured sources, avoiding custom download scraping and bundled third-party installers.

Keep the catalogue readable

Applications are plain PowerShell objects with display names and exact package IDs, making additions and reviews straightforward.

Build binaries from tags

The executable is generated on a clean Windows runner and attached to the GitHub release instead of committing generated binaries.

04

Verification evidence

  • GitHub Actions completed the v1.0.1 tagged build successfully on July 22, 2026.
  • The release contains the generated AppInstaller.exe asset with the application icon and version metadata.
  • Source inspection confirmed catalogue filtering, preserved selections, progress reporting, live logs, and explicit success or failure counts.
  • The public repository documents executable, PowerShell, batch, and Linux-script usage paths.
verified-2026-07-23
$ git push origin v1.0.1
GitHub Actions: Build and Release -> success
ps2exe -> AppInstaller.exe
release asset: v1.0.1/AppInstaller.exe
✓ tagged release verified

05

Demonstrated workflow

Winget App Installer interface with categorized application checkboxes
Searchable selection interface with progress and live logging

06

Limitations

Next step

Discuss the engineering behind this work.

Email meDownload résuméView public repository