Project Description

Exposes Windows Installer functionality to PowerShell, providing means to query installed product and patch information and to query views on packages.
PowerShell is a powerful command shell that pipes objects, not just text. Because of this ability, you can string practically unrelated commands together in many different ways to work on different types of objects, all built on .NET.

The Windows Installer extensions in this project expose cmdlets - akin to commands in a batch script - to query Windows Installer products, patches, and package databases.

Features

RFC: I'm requesting comment on how navigation should work in a provider. This would allow mounting an MSI package and browsing the package as an item provider and even copy files out as though it was another file system.

Cmdlets

• Get-MSIFileHash get the file hash in a format compatible with installation packages.
• Get-MSIFileType determines what type of MSI file - if any - a file is, optionally adding a NoteProperty to an existing FileInfo item.
• Get-MSIProductInfo gets information for installed and advertised products.
• Get-MSIPatchInfo gets information for patches applied to products, whether superseded or obsolesced.
• Get-MSIRelatedProductInfo gets information for related products based on UpgradeCode.
• Get-MSISource gets the source list for a product or patch.

Several formats are provided for many of the cmdlets.

Recommend

If there are additional features you'd like to see, please discuss on the thread Feature Ideas, or file a new Feature request if you have some concrete ideas in the Issue Tracker.

Examples

Types sent through the pipeline by these cmdlets are designed to work with standard cmdlets so you can string many cmdlets together. See Examples for a few ideas of what you can do with Windows Installer PowerShell Extensions.