-
Notifications
You must be signed in to change notification settings - Fork 546
Add Appx capabilties #1936
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Add Appx capabilties #1936
Conversation
|
Technically the ability to read the manifest information from an installer would be easily implemented as the bundle can be read as zip and the manifest file could be extracted. |
|
Sorry, Next was a temporary branch, this PR was not closed intentionally. @mjr4077au will be in touch! |
|
After discussion with @mjr4077au this will require #1925. |
|
The commit I just pushed already implements #1925, without full wiring in the toolkit yet. I also dropped everything except the Nearly all logic is now packed into the new Sorry @mjr4077au, I had to force push because most of the changes you applied were not relevant anymore. The ones that still were I tried to apply where applicable. |
The implementation shown provides the c# backend to work with Appx packages.
A demo implementation was added to
Get-ADTApplicationto preview its capabilities.The function implementation is limited to provisioned packages, as this reflects "system installed" packages equivalent to how ARP entries are queried.
The backend exposes methods to work with both provisioned and installed packages, either per user or any.
All methods are purely static and work solely on an identifier basis.
I avoided adding requirements for the Windows SDK to handle appx management to reduce external dependencies.
Information about packages is extracted from the registry and the manifest files they point to.
Filtering for family names is supported, however currently there is no property to expose this property in
InstalledApplication.