Inspect MSIX Properties via cmd or Powershell

%3CLINGO-SUB%20id%3D%22lingo-sub-2883221%22%20slang%3D%22en-US%22%3EInspect%20MSIX%20Properties%20via%20cmd%20or%20Powershell%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2883221%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%3C%2FP%3E%3CP%3EAs%20the%20title%20suggests%2C%20I%20was%20wondering%20if%20it's%20possible%20to%20inspect%20the%20properties%20of%20MSIX%20packages%20without%20installing%20them.%20Being%20able%20to%20do%20this%20would%20assist%20in%20automations%20I'm%20attempting%20to%20build%20in%20Azure.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESo%20far%20I've%20discovered%20they%20can%20be%20accessed%20with%20the%20cmdlet%20'Expand-AzWvdMsixImage'.%20This%20is%20useful%20and%20is%20being%20levered%20at%20that%20point%20in%20the%20process.%20However%2C%20earlier%20on%20the%20process%20before%20Azure%20is%20in%20play%20the%20properties%20will%20need%20to%20be%20inspected%20so%20various%20folders%20and%20groups%20can%20be%20created%20or%20located.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20properties%20I'm%20most%20interested%20in%20at%20the%20moment%20are%3A%3C%2FP%3E%3CP%3EName%3C%2FP%3E%3CP%3EPackageFullName%3C%2FP%3E%3CP%3EPackageFamilyName%3C%2FP%3E%3CP%3EVersion%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20suspect%20others%20may%20be%20of%20interest%20later.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E
Occasional Contributor

Hi,

As the title suggests, I was wondering if it's possible to inspect the properties of MSIX packages without installing them. Being able to do this would assist in automations I'm attempting to build in Azure.

 

So far I've discovered they can be accessed with the cmdlet 'Expand-AzWvdMsixImage'. This is useful and is being levered at that point in the process. However, earlier on the process before Azure is in play the properties will need to be inspected so various folders and groups can be created or located.

 

The properties I'm most interested in at the moment are:

Name

PackageFullName

PackageFamilyName

Version

 

I suspect others may be of interest later. 

 

 

1 Reply
You'd need someone to build a tool to extract out the manifest and then those fields. I'm not aware of any that you'd want.

A simpler method to accomplish what you want would be to use a file naming convention such as is adopted by some tools that generate MSIX packages. For example, PackageName_Version_Architecture_Hash.msix would allow you construct all of those fields from the filename. If these are all inhouse apps you have control of that, if from third parties you'd have to determine each and rename the files.