PowerShell Pro Tools
Ironman SoftwareGitHub
  • About
  • System Requirements
  • PowerShell Tools Documentation
    • Visual Studio
      • Analysis
      • Debugging
        • Local Debugging
        • Remote Debugging
      • Format Document
      • Go to Definition
      • Packaging in Visual Studio
      • PowerShell 7 Support
      • PowerShell Interactive Window
      • Project System
        • Advanced
        • Debug
        • Build Events
      • Settings
        • General
        • .editorconfig
        • Analysis
        • Diagnostics
      • Tool Windows
      • Refactoring
      • Unit Test Adapter
      • User Interface Design
        • Windows Forms
  • PowerShell Pro Tools Documentation
    • Visual Studio Code
      • Automating Visual Studio Code
      • Code Conversion
      • Debugging
        • Run in New Terminal
        • One-Click Attach
      • Decompiler
      • Diagnostics
      • Enhanced Hover
      • Generating a UI from a function
      • Generate a Tool from a Function
      • Packaging in Visual Studio Code
      • Pin Session
      • PowerShell Explorer
      • Profiler
      • Sign On Save
      • RapidSense
      • Refactoring
      • Rename Symbols
      • Quick Scripts
      • Windows Forms Designer
    • Installers
    • Packaging
      • Package.psd1
      • PowerShell Packager
      • Package Hosts
      • Package as Service
      • Packaging on Linux
      • Packaging on Mac OS X
      • Continuous Integration
      • Anti-Virus
    • PowerShell Module
      • Global Hotkeys
      • Show-PSEditor
      • Show-PSScriptPad
      • Show-TUIDesigner
      • ConvertTo-CSharp
      • ConvertTo-PowerShell
      • Merge-Script
      • Install-PoshProToolsLicense
      • about_MergeScriptConfig
      • Show-WinFormDesigner
    • PowerShell Protect
      • Getting Started
      • Installation
      • Actions
      • Rules
      • Configuration
    • PSCommander
    • PSScriptPad
    • Installation and Licensing
      • Visual Studio Offline Installation
  • Changelog
    • PowerShell Tools for Visual Studio
    • PowerShell Pro Tools for Visual Studio Code
    • PowerShell Packager
    • PSScriptPad
    • PowerShell Pro Tools Module
Powered by GitBook
On this page
  • Properties
  • Root Script
  • Package Referenced Scripts
  • Package Referenced Modules
  • File Properties
  • Application Properties
  • Output Path
  • Certificate
  • Diagnostic Logging
  1. PowerShell Pro Tools Documentation
  2. Packaging

PowerShell Packager

Packager PowerShell scripts as executables.

PreviousPackage.psd1NextPackage Hosts

Last updated 1 year ago

Download from the .

The PowerShell Packager uses the same packaging tools as the PowerShell Pro Tools module and PowerShell Pro Tools for VS Code but provides a simple interface that does not require configuration files or special build tools. This tool currently only supports Windows PowerShell executables.

Running the packager will provide a simple wizard that you can step through to provide details for the resulting executable.

Properties

Root Script

The root script is the script that will run when the executable is run. You can dot source other scripts and import modules in this script. This script will also receive the parameters passed to the executable.

Package Referenced Scripts

Any dot-sourced script referenced in the root script will be packaged as well. If those scripts include other dot-sourced scripts, they will also be included and so on.

Package Referenced Modules

Any module imported with Import-Module will be included with the executable.

File Properties

These are the properties that will be set on the resulting executable. For example, File Version, Description and Company name.

Application Properties

These are properties of the application itself. These include hiding the console window and Windows UI support.

Output Path

The folder path to output the resulting executable to.

Certificate

The certificate is optional and will cause the packager to call Set-AuthenticodeSignature against the executable. The certificate path should be a certificate provider path.

Cert:\LocalMachine\My\1111DDDDD

Diagnostic Logging

The packager will automatically write diagnostic logs to the following location.

$Env:LOCALAPPDATA\PowerShellTools\PSPackager
PowerShell Pro Tools download page