Bug 514 - MSI package with Windows client
Summary: MSI package with Windows client
Alias: None
Product: ThinLinc
Classification: Unclassified
Component: Client platforms (show other bugs)
Target Milestone: LowPrio
Assignee: Peter Åstrand
Depends on:
Reported: 2004-04-16 16:59 CEST by Peter Åstrand
Modified: 2021-02-03 13:03 CET (History)
1 user (show)

See Also:
Acceptance Criteria:


Comment 1 Peter Åstrand cendio 2004-08-02 11:20:58 CEST
There are devel tools available from
Perhaps these would work with Wine. 

http://blogs.msdn.com/robmen/archive/2003/11/25/56510.aspx is also interesting. 

The main question is if we *want* MSI. The discussion on the Inno Setup mailing
lists indicates that MSI is an endless source of problems. OTOH, Python 2.4 is
now delivered as an MSI, and they claim that this is superior. 

What would be really cool would be a rpm2msi, written in Python :-)
Comment 3 Henrik Andersson cendio 2015-02-13 07:49:46 CET
For reference, here [1] is an open source project with tools to generate MSI packages. The project has been around since 2004 and is still active.

[1] http://wixtoolset.org/
Comment 4 Pierre Ossman cendio 2015-10-29 15:29:51 CET
And now there are tools on Linux as well:


They are compatible with WiX, which means we could use msitools for our builds and WiX for the customizer.
Comment 5 Pierre Ossman cendio 2015-10-29 15:30:15 CET
Microsoft's sales pitch for MSI:

Comment 6 Pierre Ossman cendio 2021-02-03 13:03:22 CET
Microsoft now prefers .Appx bundles. They are normally used for Microsoft Store, so it is unclear what limitations they might have. E.g. only managed applications, and only Windows 10?

Note You need to log in before you can comment on or make changes to this bug.