Does this strike anyone else as Rube Goldberg-like? A setup program that
extracts a setup and msi and calls that setup which at the end calls the
msi.
I'm looking forward to WIX adding this functionality.
Again, thank you for all the help. What/how to do this is not easy or
intuitive so the help here has been invaluable.
Thanks - dave
David Thielen
www.windwardreports.com
303-499-2544 x1185
Cubicle Wars - http://www.windwardreports.com/film.htm
________________________________
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Rob
MacFadyen
Sent: Wednesday, December 06, 2006 5:25 PM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] bootstrapper - final questions (I think)
David,
For #1: The UI is _not_ configurable (with the exception of the title of
the dialog boxes).
The best way to structure this is to create a Self Extracting EXE that
holds the Setup.exe and your MSI. Configure the Self Extracting EXE to
run Setup.EXE when it is unpacked. ChilkatSoft.com offers a free tool to
do this:
http://www.chilkatsoft.com/ChilkatSfx.asp
The also offer a component you can use that offers a few more options.
For #2: In the GenerateBootstrapper element there is a Culture and
FallbackCulture attributes. These control the language. If you examine
the following directories:
C:\Program Files\Microsoft Visual Studio
8\SDK\v2.0\BootStrapper\Packages you will see under each directory, like
dotnetfx, a sub directory titled "en" (if you're using english). If you
examine the Package.xml file you'll see the localized strings and the
url's for the actual downloads.
It's a good question where/how to get the other languages (I don't
know... you could "brute force it" by installing VS2005 in a virtual PC
in all the languages you need).
If you need more than one language you will need to generate more than
one Setup.exe. It _ought_ to be simple enough to stuff each Setup.exe in
a subdirectory by culture (so you end up with en\Setup.exe,
es\Setup.exe, fr\Setup.exe and so on). You would then need a quick and
dirty front end that offers a "please pick language" facility and then
invokes the appropriate setup. Or you could just have separate downloads
for each language.
#3 and #4 are not handled by the GenerateBootstrapper at all. Generally
these sort of requirements are handled by your actual MSI. The general
scheme is to detect whether or not a requirement has been met and if not
display a message say "missing component X". For an improved user
experience you could show a single dialog that lists all the required
components and whether or not they are present (only show the dialog if
at least one is missing).
Detecting IIS is fairly easy in v3:
link with WixIIsExtension.dll and then the following "just
works":
<PropertyRef Id="IISMAJORVERSION"/>
<Condition Message="IIS version 5 or 6 must be installed
([IISMAJORVERSION])">
Installed OR (IISMAJORVERSION = "#5" OR IISMAJORVERSION =
"#6")
</Condition>
Not sure about Wix v2.
Hotfixes might not be too bad to detect if they show up in Add/Remove
Programs. If you can determine thee upgradecode/productcode for each
hot fix, then the <Upgrade> elements should be able to help... make sure
OnlyDetect is set though. Take a gawk at:
http://www.tramontana.co.hu/wix/lesson4.php
Regards,
Rob
________________________________
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of David
Thielen
Sent: Wednesday, December 06, 2006 6:15 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] bootstrapper - final questions (I think)
First off - THANK YOU very much to everyone who helped and in particular
Erv Walter.
I think I have it working. A couple of questions:
1. If all the prerequisites exist and I use ApplicationUrl what
happens is a window pops up for a split second, goes away, and then
nothing while it is downloading. Then our program pops up. Is there some
way to get a message while this is happening, preferably with a status
bar? Otherwise people are going to think it just went away - especially
if their download speed is slow.
1. Note - this is only an issue if all prerequisites are
already installed. If a prerequisite needs to be installed then this
download will show with a status bar.
2. If that cannot be done, what's the best way to structure
this? It seems to me it is have a MSI that holds setup.exe and our MSI,
it installs both, runs setup.exe and it calls the other MSI locally at
the end. But this means we then have 2 MSIs and that's ugly. Any other
approaches?
2. Any idea what to put in for the .NET 2.0 and J# 2.0 language
packs?
3. Any idea what to put in to get the Office hotfixes (listed at
http://www.windwardreports.com/office_hotfix.htm) to install? Two of
them for Word 200/2002/2003 and one for Word 2003 only.
4. Any idea how to make IIS a prerequisite (sort-of essential for
an ASP.NET app).
Thanks - dave
David Thielen
www.windwardreports.com <http://www.windwardreports.com>
303-499-2544 x1185
Cubicle Wars - http://www.windwardreports.com/film.htm
<http://www.windwardreports.com/film.htm>
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
