> For the complete documentation index, see [llms.txt](https://docs.poshtools.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.poshtools.com/powershell-pro-tools-documentation/packaging/powershell-packager.md).

# PowerShell Packager

{% hint style="info" %}
Download from the [PowerShell Pro Tools download page](https://ironmansoftware.com/powershell-pro-tools/downloads).
{% endhint %}

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. 

<figure><img src="/files/BQ9QPJsdUc7ga1VdgSrz" alt=""><figcaption></figcaption></figure>

## 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.&#x20;

### 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.&#x20;

### Package Referenced Modules

Any module imported with `Import-Module` will be included with the executable.&#x20;

### File Properties

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

### Application Properties

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

### Output Path

&#x20;The folder path to output the resulting executable to.&#x20;

## 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.

```powershell
Cert:\LocalMachine\My\1111DDDDD
```

## Diagnostic Logging

The packager will automatically write diagnostic logs to the following location.&#x20;

```powershell
$Env:LOCALAPPDATA\PowerShellTools\PSPackager
```


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.poshtools.com/powershell-pro-tools-documentation/packaging/powershell-packager.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.