Bob Arnson <[EMAIL PROTECTED]>
Subject: Re: [WiX-users] Custom UI Dialog errors
To: "General discussion for Windows Installer XML toolset."
<wix-users@lists.sourceforge.net>
Message-ID: <[EMAIL PROTECTED]>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Dane Anderson (Volt) wrote:
> I am attempting to create a trial Custom UI (my first). Nothing spectacular,
> just a single dialog box
> with a single edit control, and a next button (fancy will come later after I
> get THIS to work).
>
There's a bunch of minimum requirements you have to meet if you have any
UI in your package. That's what the ICE errors are telling you.
I'd suggest using WixUI instead of entirely rolling your own. Otherwise,
see the MSI SDK topic "Using the User Interface" for the content you'll
need.
*****************************************
I'm afraid that the WixUI built in dialogs won't do what I need to do.
I have 6-9 properties that would normally be set on the command line,
but we are anticipating testers that will be starting the install by
dbl clicking on the msi file icon. The properties have defaults, but
the defaults may NOT be what the testers need them to be, so I have
been tasked with providing a UI that they can use to see the defaults,
and change them if necessary. As far as I know there are no pre-defined
dialogs that do what I need to do. THAT in itself should be understandable
as the Wix Documentation does not seem to document ANY of the pre-defined
dialogs (it defines only the predefined UI sequences WixUI_Mondo,
WixUI_FeatureTree, WixUI_InstallDir). Is there a place where all these
pre-defined dialogs are documented? They are not in the Wix documentation
that comes with the Wix install package (I know, I've read it and searched
it from the the front to the back. Unless I missed seeing them accidentally
they (the dialogs) are NOT there)
I managed to fix the problem the compiler/linker had with the missing
FilesInUse dialog,
by adding:
<Show Dialog="FilesInUse" OnExit="suspend" />
to the InstallUISequence element (Whether that will work correctly or not is
a question I will have to find out later) , and:
<Binary Id="WixUI_Bmp_Banner" SourceFile="Binary\Banner.bmp" />
to the UI element (because it wanted the banner defined in the binary table).
That leaves me with the error dialog. I added:
<Property Id="ErrorDialog" Value="TerminalError" />
To fix the problem with the ErrorDialog Property not being in the property
table,
and added a TerminalError dialog which has a control (type text) ErrorText (as
its
first child), BUT the compiler/linker want that ErrorText element to be flagged
as
Control_First. The Wix documentation I have doesn't mention Control_First
ANYWHERE.
So, how do, from inside my wxs file, I flag that ErrorText element as the
Control_First for the error dialog? I suspect that it will be an attribute of
the
dialog, or the control, but the Wix docs don't say, and the VS drop down hints
don't
contain anything that appears to be correct.
Oh, the suggestion to look in MSI SDK topic "Using the User Interface" helped a
little. At least it gave me some clues about where to look in the Wix
documentation.
It also helped me find the ICE Reference
( http://msdn.microsoft.com/en-us/library/aa369206(VS.85).aspx ).
That helped me to figure out what was needed.
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
