dthree/cash

MSI Installer

Open

#9 opened on Feb 24, 2016

View on GitHub
 (20 comments) (0 reactions) (0 assignees)JavaScript (7,768 stars) (253 forks)batch import
enhancementhelp wanted

Description

What all did you need for an installer? Depending on how complex you need it, I (or others) might be able to help. A couple things about installers:

  • For generating vanilla MSI Windows installers, WiX is the usual means. All the configuration is stored in XML, and it can work with Visual Studio or as a standalone tool. It can do most everything, but it requires a fair amount of knowledge to do more complex tasks. Simple folder deployments are very straightforward, though.
  • There's a lot of other installation systems, like InstallShield or NSIS that get used a lot due to be being relatively simplistic. Most often they get deployed as executable assemblies (EXEs) instead of installers.
  • You can do fancy UI wrappers around the installers (with EXE wrappers) and some limited internal UI changes, too, but I generally wouldn't bother. There are templates that give you the standard Welcome/License/Installation Path UX.
  • Building installers from non-Windows systems can be a pain. WiX requires WINE to build on Linux due to a dependency on MSI.DLL. There's a Gnome project, MSITools, that has a partial WiX implementation but finding documentation on it is a pain, so I haven't bothered looking into it.

So what did you need the installer to actually do? And is it okay if it only builds on Windows?

Contributor guide