Jul 13 2021 04:06 PM - edited Jul 13 2021 04:12 PM
The conversion of MSIX packages to CimFS includes defining a "root folder", the name of which appears irrelevant. If I call it "George", when deployed, this creates a folder structure that looks like:
\\?\Volume{GUID}\George\{FullPackageFamilyName}
as the actual "root folder" of the original MSIX package (the one that contains the metadata files).
This raises the question as to whether multiple packages may be included within the CIM image (under "George"), and if so what relationships are expected/allowed. For example,
Also, is there a requirement that {FullPackageFamilyName} be the name of the second level folder or is that just what the conversion tools currently do and the name of that folder is also irrelevant? As the mounting process hides that name from MSIX I'm guessing the latter, unless there is a plan for AppInstaller to use it in decision logic.
Even if not available today, as I'm building CIM based tooling I'd like to know more about what could be or is clearly not in scope for the future in this regard.
Sep 14 2021 10:27 AM