Rob Hamflett wrote:
> There are a few things you could consider.
Hi Rob.
> You could ask the
> other company to produce a merge module for you.
I did that, and they said 'no'. I am not too happy to depend
on that third party software, unfortunately there's no way
to replace this soonish.
Moreover, I came to the (possibly wrong) conclusion that
'Merge module' and 'Merge module' might be different beasts.
I had troubles to use merge modules produced by ("plain")
Visula Studio Merge Module porjects in a Wix based installer,
possibly due to the way the merge is actually done (Wix
seems to resolve the merging at link time whereas the
VS deployment stuff resolves them at install time, at least
that's my guess right now). So if this assumption is true,
even a merge module might not be enough since it might be of
the wrong breed.
> There is also a custom action type for launching another MSI file,
> but you'll have to run it during the UI Sequence.
That'd be interesting.
Let me try to figure out how this works.
>From the Wix Schema page I end up somewhere near
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/msi/setup/summary_list_of_all_custom_action_types.asp
which does not seem to contain something directly related to
starting another install. I can, of course, start 'msiexec',
but that yields the 'two installers at the same time' problem.
So maybe there are more 'native' custom action types then those
listed on that page?
> The problem here is that there's no possibility of rollback, and
> you can't get at the embedded MSI file if it's wanted for
> anything else like repairs.
Repair would not be that much of an issue as this would be new
functionality for our users anyway - so it'd be ok if it were
absent or 'semi-broken'.
What do you mean by 'no possibility of rollback' exactly?
That if the installer has to exit after the installation
of the embedded product there'd be no way to clean this
up, i.e. the embedded product would remain installed?
That'd be a problem I suppose...
> The recommended method is to use a bootstrapper which installs
> all the pre-requisites and then installs your own product.
Ok, we sort of have this kind of setup right now already in a
non-msi world. I had thought in beginning we could get rid
of it once everything uses msi... well...
Thanks for your input.
Andre'
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
