Skip to content
This repository was archived by the owner on Sep 26, 2021. It is now read-only.
This repository was archived by the owner on Sep 26, 2021. It is now read-only.

MSI for Windows Installer #180

Open
Open
@zaps

Description

@zaps

I'm working on a fork of Toolbox to utilize MS Windows Installer (using WiX) to provide a more native installation experience than the current InnoSetup implementation. Using MSI reduces the amount of abstraction added by third-party install solutions like Inno because Windows Installer is baked into the OS itself, so there is less script-driven acrobatics needed for example, to set environment variables, and more declarative approach. There are also benefits from an upgrade/patching standpoint.

I was curious if there was any design documentation that exists w/r/t the current Windows installer. Things like file locations, order of dependent package installation, upgrade scenario requirements, etc. I am somewhat familiar with Inno so I'm slowly trying to translate the behavior into a Windows Installer equivalent but if there was something already that laid all this info out it would make it much easier to work with.

There are also questions that come up during the course of this work that I am unsure the reasoning of. Such as why is the installer using the Kitematic .zip file and decompressing its contents instead of using the pre-built setup.exe provided by the Kitematic team? If there were documentation, I could understand the reasoning behind this decision.

Thanks in advance!

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions