First of all the actions in InstallUISequence are performed which is
generally where the user selects what they want installed and where they
install it. When this is done the installer makes a script which
includes the stuff from the InstallExecuteSequence. This is handed off
to the Windows installer and the actual install is performed. To get a
good idea of what's going on during an install run it with the logging
options. "msiexec /i <msi file> /lieavx" should do. There are more
logging options but they're probably a bit heavy going to start with.
You're best off getting the Platform SDK and then going through the
first example on
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/msi/setup/windows_installer_examples.asp.
This'll get you started with MSI, and hence WiX. To get the SDK you
want to go to http://www.microsoft.com/msdownload/platformsdk/sdkupdate/
with Internet Explorer and get the Windows Installer SDK Version 2.0.
The SDK will also give you an installer for Orca in C:\Program
Files\Microsoft SDK\Bin. If you don't have this you'll probably want
it. It's a program for opening up and editing MSI fies and I find it
invaluable (it's also needed for the examples).
Once you've been through the first example you can decompile the msi
file with "dark MNP2000.msi MNP2000.wxs /x ."
MNP2000.msi is the name of the install that you'll make in the example.
MNP2000.wxs is the resultant wix file and /x <path> means extract the
binary information. The "." after the "/x" will use the current
directory and you'll find an Icon and a Binary directory has been made.
You can then open up the newly made wxs file and have a look at the
contents of the UI tag to find out how the GUI is put together. Even if
it's not exactly what you want, it should be enough for you to look at
and tinker with. It's how I worked out how to make GUIs.
Hope that's been of help,
Rob
Roel Vanhout wrote:
> Hi all,
>
> I'm trying to get a grip on msi (using wix) but I'm having trouble
> understanding the event system. I'm trying (as an exercise) to make a
> simple installer that has a welcome screen with an 'ok' button and
> that installs an empty file after the user clicks 'ok' on that button.
> Now, what I don't understand is how the 'actions' in InstallUiSequence
> and InstallExecuteSequence relate. In what order are they executed?
> It's not first the actions in the one and then those in the other,
> right? And how do I specify 'start installing when I press the ok
> button', and if I wanted to display a progress dialog, how do i
> specify 'show another dialog and start installation at the same time'?
> Thanks.
>
>
> cheers,
>
> roel
>
--
The views expressed in this message do not necessarily constitute the views of SN Systems Ltd and information in this message is confidential and may be privileged. It is intended solely for the person to whom it is addressed. If you are not the intended recipient, please notify the sender and please delete the message from your system immediately.
|
