get-componentinfo does attach a PSPath to each component, but when piped to get-childitem (dir) the explicit "Path" property is used for binding, which means any registry paths are not processed ri...
Id #14475 | Release:
| Updated: Nov 1 at 12:38 AM by heaths | Created: Oct 31 at 9:20 PM by heaths
It appears that the installer package will only install to the current user's module folder. Please add an option to install for all users on the machine.
I've used this package to script msi ins...
Id #14474 | Release:
| Updated: Nov 1 at 9:18 PM by heaths | Created: Oct 25 at 5:39 PM by mzboray
Create a script cmdlet to wrap this snippet. It must take patches into account, and get-msiproductinfo | get-msifeatureinfo does just that.
Id #14471 | Release:
| Updated: Jul 3 at 10:14 PM by heaths | Created: Jul 3 at 10:14 PM by heaths
Curently get-msicomponentinfo is always attaching the PSPath property as a NoteProperty, which means the RegistryView code must be executed every time regadless of whether the PSPath property is us...
Id #14470 | Release:
| Updated: Jul 3 at 2:06 PM by heaths | Created: Jul 3 at 2:06 PM by heaths
Modifying the source list is possible through the Installation-driver classes, but isn't obvious to anyone that doesn't know DTF or doesn't use get-member to view type members. Consider adding cmdl...
Id #14462 | Release:
| Updated: Jun 21 at 2:34 AM by heaths | Created: Jun 11 at 6:04 PM by heaths
Create a provider for mounting MSI files as PSDrives so that users can navigate and copy out of the media.
Id #5778 | Release:
| Updated: May 20 at 5:39 PM by heaths | Created: Mar 18, 2008 at 7:04 PM by heaths