May 26 2020 09:21 PM
May 26 2020 09:21 PM
2 quick questions:
Jun 03 2020 10:43 AM - edited Jun 03 2020 10:44 AMSolution
@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.
Jun 03 2020 11:30 AM
@TIMOTHY MANGAN Thank you for your response Tim. Notepad++ which derives it FTA via .dll file seems to be one of those apps.
Yeah something similar to connection group should be there for MSIX as well. Thank you for shedding some light on which type of apps are ideal to be created as optional packages via Modification package approach.
Jun 04 2020 06:52 AM
@DS2803 Modification packages seem good as:
When it comes to files, Modification packages (currently) require VFS pathing to be used for the overlay to work. So you don't tell the packaging tool where notepad++ is going to be installed so that all files are VFS'd. Due to an implementation oversite, this overlay does not work on operating systems prior to 1904.
Jun 04 2020 12:14 PM
Another option you can look at for sharing resources between two applications deployed as separate packages is packaging them as a related set.
You can find more details here:
Jun 09 2020 11:15 PM
@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.