Skip to main content

Extracted Archive

The PSAppDeployToolkit archive, when unziped, archive package consists of the following folders and files, and should reflect what you see when you unzip the PSAppDeployToolkit archive:

Toolkit/
โ”œโ”€โ”€ Deploy-Application.ps1
โ”œโ”€โ”€ Deploy-Application.exe
โ”œโ”€โ”€ Deploy-Application.exe.config
โ””โ”€โ”€ AppDeployToolkit/
โ”œโ”€โ”€ AppDeployToolkitBanner.png
โ”œโ”€โ”€ AppDeployToolkitConfig.xml
โ”œโ”€โ”€ AppDeployToolkitExtensions.ps1
โ”œโ”€โ”€ AppDeployToolkitHelp.ps1
โ”œโ”€โ”€ AppDeployToolkitLogo.ico
โ”œโ”€โ”€ AppDeployToolkitMain.cs
โ””โ”€โ”€ AppDeplotToolkitMain.ps1

Examples/
โ”œโ”€โ”€ AdobeReader/
โ”‚ โ””โ”€โ”€ Deploy-Application.ps1
โ””โ”€โ”€ Office2013/
โ””โ”€โ”€ Deploy-Application.ps1
PSAppDeployToolkit.pdf
CHANGELOG.txt
LICENSE.txt

File & Folder layoutโ€‹

Here we will examine each of the files and folders and describe their function:

Root folderโ€‹

Folder NameDescription
Toolkit/Contains PSAppDeployToolkit itself and all of the files / folder structure required to create a deployment package.
Examples/Contains example deployments for both Adobe Reader and Microsoft Office 2013.
PSAppDeployToolkit.pdfDeprecated - A PDF with all docuementation. This has proven difficult to maintain. We hope that recent chagnes to the website will mean this can be removed.
CHANGELOG.txtThe changelog for the current release of the PSAppDeployToolkit.
LICENSE.txtThe LGPL license under which the PSAppDeployToolkit is distributed.

Toolkit Folderโ€‹

This contains all of the files needed to create a new deployment package

Folder / File NameDescription
AppDeployToolkit/Contains the PSAppDeployToolkit dependency files.
Files/Contains the primary installation file(s), e.g. MSI file. This folder is empty by default.
SupportFiles/Contains any supporting resources or assets, e.g. files you need to copy to the target machine using the PSAppDeployToolkit during deployment. This folder is empty by default.
Deploy_Application.ps1PowerShell script that contains the logic to perform the actual install / uninstall / repair. This is the only file that needs to be modified, depending on your level of customization.
Deploy-Application.exeAn optional executable that can be used to launch the Deploy-Application.ps1 script without opening a PowerShell console window. Supports passing command-line parameters to the script.
Deploy-Application.exe.configA .NET configuration file required for Deploy-Application.exe to function correctly.

AppDeployToolkit Sub-Folderโ€‹

File NameDescription
AppDeployToolkitBanner.pngThe default PSAppDeployToolkit branded header, used on any messaging displayed to the end user if interaction is reqauired. To brand the PSAppDeployToolkit User Interface with your own custom / corporate banner, replace this file with your own image. The file must be in PNG format and must be 450 x 50 in size.
AppDeployToolkitConfig.xmlPSAppDeployToolkit global configuration file. Used by the AppDeployToolkitMain.ps1 script, and sets default values for how the toolkit should behave overall. This is intended to be a static file that is configured once, not on a per-deployment basis.
AppDeployToolkitExtensions.ps1This is an optional PowerShell script that can be used to extend the PSAppDeployToolkit functionality with custom functions. It is automatically dot-sourced by the AppDeployToolkitMain.ps1 script.
AppDeployToolkitHelp.ps1PowerShell script to display a Help consoleThis is a script that displays a help console to browse the functions included in the PSAppDeployToolkit and copy and paste examples in to your deployment script.
AppDeployToolkitLogo.icoContains the default PSAppDeployToolkit branded icon. To brand the balloon notifications and UI window title bars with your own custom / corporate logo, replace this file with your own icon.
AppDeployToolkitMain.csContains additional classes and methods referred by the AppDeployToolkitMain.ps1 script.
AppDeployToolkitMain.ps1Contains all of the functions and logic used by the installation script. By Separating the logic from the installation script, we can obfuscate away the complex code and make enhancements independently of the installation scripts that contain per-application actions.