line option.
[2]
http://msdn.microsoft.com/library/en-us/msi/setup/bootstrapping.asp?fram
e=true
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Magus
> Sent: Wednesday, August 16, 2006 1:15 PM
> To: wix-users@lists.sourceforge.net
>
Magus wrote:
> Interesting how that doesn't seem to have anything to do with wix. I
have no idea how to write a program for MSI
But that's *exactly* what WiX does. If you are writing WiX code you are
generating an MSI database. WiX just gives you an easier (and in my
opinion) better way to do so
Interesting how that doesn't seem to have anything to do with wix. I have no
idea how to write a program for MSI, I've tried finding tutorials, but I
have been unsuccessful. I am not an SQL guy either, I don't know how are
when to use MsiSetExternalUI(), exect that its not something I can call fro
There are external UIs that can "skin" a MSI file. From what I understand, the skinning application/engine builds an EXE that contains the MSI file. The EXE is a boot-strapper of sorts that executes the MSI file, but hooks in its own UI. You can find one at http://www.skincrafter.com/installer.h
For requirement 1, it seems your best bet may be to make a small wizard
application that displays the Welcome/Splash screen and the combined license
agreement. At the end of the wizard, your MSI is run with
MsiInstallProduct(). The MSI would then have the other dialogs such as
feature selection t
5 matches
Mail list logo
