In article <1240352013685-2672846.p...@n2.nabble.com>,
lesterbangs <datapa...@gmail.com> writes:
> In this case, is it ok to run this cleanup procedure as an immediate action?
> What are the potential pitfalls of authoring the MSI in this way? Do I have
> any other alternatives apart from manually requiring the cleanup to be a
> separate step uninstall-old/reinstall-new process?
I would handle this in a custom bootstrapper that:
i) identifies if the previous version is installed and if installed:
a) backs up any data needed from the previous version
a) runs the uninstall of the previous version
b) performs the cleanup after the uninstall completes
ii) runs the install of your new version
That way you get a solution that works if they are upgrading or if
they are installing fresh.
I've dealt with these sorts of scenarios before and they are always
difficult to get right. The main suggestion I have for getting it all
completely correct is to test the hell out of it with some sort of
virtual machine software (Virtual PC, VMWare, Virtual Box, etc.) so
that you can reliably and repeatably test the process.
--
"The Direct3D Graphics Pipeline" -- DirectX 9 draft available for download
<http://www.xmission.com/~legalize/book/download/index.html>
Legalize Adulthood! <http://blogs.xmission.com/legalize/>
------------------------------------------------------------------------------
Stay on top of everything new and different, both inside and
around Java (TM) technology - register by April 22, and save
$200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco.
300 plus technical and hands-on sessions. Register today.
Use priority code J9JMT32. http://p.sf.net/sfu/p
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
