From wpf-dev-pack
Guides publishing WPF apps with deployment methods (framework-dependent, self-contained, single-file) and installer options (Velopack, MSIX, NSIS, Inno Setup). Useful for publish, deploy, release, packaging queries.
How this skill is triggered — by the user, by Claude, or both
Slash command
/wpf-dev-pack:publishing-wpf-appssonnetThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
When publishing WPF applications, ask the user about deployment and installer preferences.
When publishing WPF applications, ask the user about deployment and installer preferences.
Which deployment method do you need?
- Framework-Dependent - Small size (~1MB), requires .NET runtime
- Self-Contained - Includes runtime (150-200MB), no dependencies
- Single-File - One executable (50-80MB compressed)
Which installer/update technology do you prefer?
- Velopack (Recommended) - Modern, fast updates, delta updates
- MSIX - Windows Store, enterprise deployment
- NSIS - Traditional installer, full control
- Inno Setup - Simple, widely used
- None - Portable/xcopy deployment
| Method | Size | Startup | Requirements |
|---|---|---|---|
| Framework-Dependent | ~1MB | Fast | .NET runtime |
| Self-Contained | 150-200MB | Fast | None |
| Single-File | 150-200MB | Medium | None |
| Single-File + Compressed | 50-80MB | Slower | None |
| Technology | Auto-Update | Delta Updates | Store | Complexity |
|---|---|---|---|---|
| Velopack | ✅ | ✅ | ❌ | Low |
| MSIX | ✅ | ✅ | ✅ | Medium |
| NSIS | Manual | ❌ | ❌ | High |
| Inno Setup | Manual | ❌ | ❌ | Medium |
⚠️ PublishTrimmed: Not supported (reflection-heavy) ⚠️ PublishAot: Not supported (WPF incompatible)
# Framework-Dependent
dotnet publish -c Release
# Self-Contained
dotnet publish -c Release -r win-x64 --self-contained true
# Single-File (WPF)
dotnet publish -c Release -r win-x64 --self-contained true \
-p:PublishSingleFile=true \
-p:IncludeNativeLibrariesForSelfExtract=true
npx claudepluginhub christian289/dotnet-with-claudecode --plugin wpf-dev-packSelecting a .NET UI framework. Decision tree across Blazor, MAUI, Uno, WinUI, WPF, WinForms.
Packages WinUI 3 apps into MSIX installers, handles certificate generation/trust, code signing, self-contained deployment, and CI/CD. Use for release preparation or Store submission.
Packages a local web project as a Windows desktop app with a Start Menu shortcut, .exe launcher, and Taskbar identity. Mirrors macOS app-it contract (soft-close vs quit, warm dev-server reuse). Beta — requires Windows maintainer to verify hardware-dependent steps.