Forum Discussion
MSIX - FTA and Dependency handling
DS2803 Some possible answers.
1) An application may have more than one FTA.
2) Support for Shell Extensions (FTA items under ShellEx that point to dlls to be loaded by the windows shell "windows explorer" process) is sketchy at present. Some types work and some don't. I'm unaware of a published list, but context menus are the most popular type and they seem OK.
3) The equivalent of the App-V Connection group has been discussed as a possible (likely?) future for MSIX. Of course it has to have a different name when it comes out. There is a also a different concept called the Modification package. A modification package depends on a primary package and may contain files and registry, but no outward publishing extensions like shortcuts/FTAs/Protocol Handlers.
TIMOTHY_MANGAN Thank You for your reply Tim. Noticed something strange though... If my main package is removed, the optional packages related to them also gets removed. Is this expected?
I see within the manifest.xml of the optional package, I have the name of the main package as reference. If I build the next version of the main package with the same Name (Not referring to the display name here), my optional package should auto link with that.
With optional package getting auto-removed when main package is removed, it will mean I have to install optional package everytime alongside main package, which kind of beats the purpose of optional package.
Any thoughts?
DS2803 Yes, removal of main package automatically removed the optional packages.
However, if you upgrade the main package, the optional packages stay even though the old version is removed as part of that process.