Improve windows module installer support #111
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Third patch to gain Unity Hub parity for module installation. For windows it was necessary to implement other changes first to get to the point to safely implement the missing installer types.
This patch adds the missing installer types:
Zip
Zip is used as for all other platforms. It invokes the shared cross platform implementation.
MSI
The
msi
installer is tricky. It seems to be used only byFacebook Gameroom
. It seems Unity Hub expects a specigiccmd
string to replace the installer path. I use the same trick as used with theexe
installers by creating a tempcmd
script which invokes the installer comand. At one point it might be worth investigating in aCommandExt
to call the windows process in the correct way.Changes
zip
module installer supportmsi
module installer supportpo
language files installer supportcmd
string