Project

PSPublishModule

PSPublishModule is an open-source PowerShell and .NET project with packages, release history, and technical documentation.

View on GitHub Releases Get package
Stars47
Forks16
Open issues1
PowerShell Gallery downloads17213
Releasev3.0.150
Language: C# Updated: 2026-09-22T21:55:35.0000000+00:00

Curated Examples

README

DotNetPublish Examples

This folder contains starter examples for the DotNet publish engine.

Files:

  • Example.ServiceMsi.json
    • service packaging + MSI prepare/build pattern.
  • Example.GeneratedServiceMsi.json
    • service packaging + generated WiX SDK MSI authoring pattern.
  • Example.LinuxDesktopDebian.json
    • Linux desktop publish + native Debian package, command, desktop entry, MIME types, and icon.
  • Example.MacDesktopApp.json
    • macOS desktop publish + .app bundle layout, ICNS generation, channel-appropriate code signing, document associations, and transport ZIP.
  • Example.RebuildState.json
    • rebuild/state preservation pattern with service lifecycle.
  • Example.PortableBundleMsi.json
    • desktop app + service sidecar + portable bundle + MSI pattern.
  • Example.PackageBundleMsi.json
    • service/CLI package layout with README copy, module payload include, generated wrapper script, bundle post-process, and MSI from the composed bundle.
  • Example.StorePackage.json
    • desktop app + Store/MSIX packaging project pattern.
  • Example.StoreSubmit.json
    • packaged-app Partner Center submission pattern for powerforge store submit.
  • Example.StoreDesktopSubmit.json
    • MSI/EXE Partner Center submission pattern for powerforge store submit.

These are intentionally production-shaped templates. Update project/service/installer paths for your repository before running.

Typical Usage

  1. Copy one template to repo root:
Copy-Item '.\Module\Examples\DotNetPublish\Example.ServiceMsi.json' '.\powerforge.dotnetpublish.json'

For desktop/portable delivery:

Copy-Item '.\Module\Examples\DotNetPublish\Example.PortableBundleMsi.json' '.\powerforge.dotnetpublish.json'

For a Linux desktop Debian package, copy the template and run PowerForge on Linux with dpkg-deb available:

Copy-Item '.\Module\Examples\DotNetPublish\Example.LinuxDesktopDebian.json' '.\powerforge.dotnetpublish.json'

For a macOS application bundle, copy the template and run PowerForge on macOS with the system codesign, sips, iconutil, and ditto tools:

Copy-Item '.\Module\Examples\DotNetPublish\Example.MacDesktopApp.json' '.\powerforge.dotnetpublish.json'

  1. Adjust Projects, Targets, Installers, StorePackages, or Store submission paths as needed.

  2. Validate and plan:

Invoke-DotNetPublish -ConfigPath '.\powerforge.dotnetpublish.json' -Validate
Invoke-DotNetPublish -ConfigPath '.\powerforge.dotnetpublish.json' -Plan
  1. Run:
Invoke-DotNetPublish -ConfigPath '.\powerforge.dotnetpublish.json' -ExitCode

Notes

  • Example.ServiceMsi.json expects a WiX installer project (*.wixproj).
  • Example.GeneratedServiceMsi.json uses Installers[].Authoring to generate Product.wxs and a WiX SDK project during msi.build; use Type on each authoring component (File, Folder, RemoveFolder, Service, RegistryValue, Shortcut). It also shows typed finish-page launch and RTF license agreement authoring through ExitLaunch and LicenseAgreement.
  • Example.LinuxDesktopDebian.json uses Installers[].Kind = Debian and keeps Linux package layout, /usr/bin command wiring, freedesktop metadata, and dpkg-deb execution in PowerForge. The product repository supplies only declarative identity and paths.
  • Example.MacDesktopApp.json uses Installers[].Kind = MacApp and keeps .app layout, Info.plist, ICNS generation, signing, verification, and ditto packaging in PowerForge. Its CodesignIdentity = "-" is deliberately local-only proof, so PowerForge omits hardened runtime to keep multi-file apps launchable without an Apple Team ID. Direct distribution enables hardened runtime by supplying a Developer ID Application identity, a trusted timestamp, and PowerForge's Apple notarization/stapling flow.
  • Example.RebuildState.json is aimed at preserve/restore deployments and service-aware rebuild flows.
  • Example.PortableBundleMsi.json shows how to use Bundles, include sidecar targets, and build an MSI from the composed bundle instead of the raw publish output.
  • Example.PackageBundleMsi.json is the starter for TierBridge-style packages: composed service/CLI payload, shipped PowerShell module, generated scripts, ZIP, and MSI from the bundle.
  • Example.StorePackage.json shows how to keep Store/MSIX packaging in the same PowerForge publish matrix as the app target.
  • Example.StoreSubmit.json shows how to submit a packaged-app ZIP to Partner Center from the DotNetPublish manifest after StorePackages[] produces the *.msixupload or *.appxupload artifact.
  • Example.StoreDesktopSubmit.json shows how to submit MSI/EXE metadata through the newer desktop Store submission API.
  • For command naming and fast overrides, see:
    • Docs/PSPublishModule.DotNetPublish.Quickstart.md