Forum Discussion
Multi Application Suite?
This probably fits into both the deployment and the packaging channels, but we'll start here. I'm trying to work out the best way to approach deployment of a 'suite' of 4 applications. Some cust...
- In case anyone is interested, this is the approach I ended up going with: https://techcommunity.microsoft.com/t5/msix/combining-optional-packages-and-modification-packages/m-p/3432402/highlight/true#M3044
In the MSI world we'd have one installer with checkboxes to allow the admin to pick the things they want to install (which could be driven by params in a silent install) - I'm effectively trying to create something that gives them a similar deployment experience, but obviously taking into account the fact that the installer itself can't be customised, hence the idea to use appinstaller files to achieve the one-hit install by deploying the main package with the customers choice of optional packages (we'd basically give them a small guide on how to configure this themselves).
It feels like this is the best approach from my understanding so far, but perhaps the book will illuminate a different path.
It feels like this is the best approach from my understanding so far, but perhaps the book will illuminate a different path.
What stops you from building an MSI wrapper over all the MSIX packages (to deliver them as single installer for all the apps) and keeping the MSIX packages as a separate for folks that need just some of them?
In this case, the MSI would simply act as a script, without affecting the payload of the packages or leaving any garbage on the system.
In this case, the MSI would simply act as a script, without affecting the payload of the packages or leaving any garbage on the system.
