SOLVED

Multiple MSIs/EXEs with Command Line?

%3CLINGO-SUB%20id%3D%22lingo-sub-316032%22%20slang%3D%22en-US%22%3EMultiple%20MSIs%2FEXEs%20with%20Command%20Line%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-316032%22%20slang%3D%22en-US%22%3E%3CP%3EWhen%20the%20MSIX%20packaging%20tool%20is%20run%20manually%2C%20the%20documentation%20mentions%20the%20following%3A%26nbsp%3B%3C%2FP%3E%3CUL%3E%3CLI%3E%3CEM%3EIf%20you%20need%20to%20run%20multiple%20installers%20you%20can%20do%20that%20manually%20at%20this%20point.%3C%2FEM%3E%3C%2FLI%3E%3CLI%3E%3CEM%3EIf%20the%20app%20needs%20other%20pre-reqs%2C%20you%20need%20to%20install%20them%20now.%3C%2FEM%3E%3C%2FLI%3E%3C%2FUL%3E%3CP%3EHowever%2C%20it%20seems%20there%20is%20no%20way%20to%20do%20this%20when%20running%20the%20tool%20via%20the%20command%20line.%20Is%20this%20something%20on%20the%20roadmap%20to%20implement%3F%20To%20possibly%20allow%20for%20multiple%20%3CINSTALLER%3E%20nodes%3F%3C%2FINSTALLER%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20would%20like%20to%20automate%20conversion%20of%20some%20of%20our%20MSI%20packages%2C%20but%20the%20vast%20majority%20of%20the%20MSIs%20I%20will%20be%20converting%20have%20dependencies%20on%20other%20MSIs%20or%20EXEs%20that%20I%20would%20like%20to%20install%20at%20the%20same%20time%20and%20be%20captured%20for%20an%20MSIX%20without%20having%20to%20click%20through%20the%20Packaging%20Tool%20and%20respective%20installers%20each%20time.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-319703%22%20slang%3D%22en-US%22%3ERe%3A%20Multiple%20MSIs%2FEXEs%20with%20Command%20Line%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-319703%22%20slang%3D%22en-US%22%3E%3CP%3EI%20had%20also%20posted%20this%20as%20documentation%20feedback%20(%3CA%20href%3D%22https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fmsix-docs%2Fissues%2F5%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%22%3EGitHub%20Issue%3C%2FA%3E)%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHere's%20the%26nbsp%3Bcurrent%26nbsp%3Bworkaround%3A%3C%2FP%3E%3CDIV%20class%3D%22js-discussion%20js-socket-channel%22%3E%3CDIV%20class%3D%22js-timeline-item%20js-timeline-progressive-focus-container%22%3E%3CDIV%20class%3D%22timeline-comment-wrapper%20js-comment-container%22%3E%3CDIV%20class%3D%22timeline-comment-group%20js-minimizable-comment-group%20js-targetable-comment%22%3E%3CDIV%20class%3D%22unminimized-comment%20comment%20previewable-edit%20js-comment%20js-task-list-container%20timeline-comment%20reorderable-task-lists%22%3E%3CDIV%20class%3D%22edit-comment-hide%22%3E%3CTABLE%3E%3CTBODY%3E%3CTR%3E%3CTD%3E%3CP%3E%3CEM%3EThis%20is%20currently%20not%20supported%20but%20it%20is%20captured%20in%20the%20backlog.%20You%20can%20create%20a%20PowerShell%20script%20that%20runs%20all%20your%20MSIs%20or%20Setup.exes%20(or%20any%20copy%20operations)%20and%20pass%20the%20.ps1%20file%20as%20your%20installer%20argument%20in%20the%20CLI%20template%20to%20workaround%20this.%3C%2FEM%3E%3C%2FP%3E%3C%2FTD%3E%3C%2FTR%3E%3C%2FTBODY%3E%3C%2FTABLE%3E%3CDIV%20class%3D%22comment-reactions%20%20js-reactions-container%20js-socket-channel%20js-updatable-content%22%3E%26nbsp%3B%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FDIV%3E%3CDIV%20class%3D%22js-timeline-marker%20js-socket-channel%20js-updatable-content%22%3E%26nbsp%3B%3C%2FDIV%3E%3C%2FDIV%3E%3CDIV%20class%3D%22discussion-timeline-actions%22%3E%26nbsp%3B%3C%2FDIV%3E%3C%2FLINGO-BODY%3E
New Contributor

When the MSIX packaging tool is run manually, the documentation mentions the following: 

  • If you need to run multiple installers you can do that manually at this point.
  • If the app needs other pre-reqs, you need to install them now.

However, it seems there is no way to do this when running the tool via the command line. Is this something on the roadmap to implement? To possibly allow for multiple <Installer> nodes?

 

I would like to automate conversion of some of our MSI packages, but the vast majority of the MSIs I will be converting have dependencies on other MSIs or EXEs that I would like to install at the same time and be captured for an MSIX without having to click through the Packaging Tool and respective installers each time.

1 Reply
Best Response confirmed by tmccarthy (New Contributor)
Solution

I had also posted this as documentation feedback (GitHub Issue)

 

Here's the current workaround:

This is currently not supported but it is captured in the backlog. You can create a PowerShell script that runs all your MSIs or Setup.exes (or any copy operations) and pass the .ps1 file as your installer argument in the CLI template to workaround this.