The way I accomplished this was to store the install path in the
registry and then do a registry search to find out where the previous
version was installed. I believe the same thing could be accomplished
with a file search.
Property Id=DIRFOO
RegistrySearch Id=FooPath Type=directory
?
/Feature
--
/Feature
/Feature
/Product
Mike
-Original Message-
From: Stout, Mike [mailto:mike.st...@oa.mo.gov]
Sent: Friday, September 25, 2009 8:31 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Update adding
components
ever be removed? If so, by what mechanism?
The component you update (that is the DLL, Debug, Doc, and Registry,
correct?) keeps its filename and directory, correct?
Are you intending to simply ship the raw MSI file out, or are you
bootstrapping it?
-Original Message-
From: Stout
I am new to writing set up packages in general and I am looking for a
way to have a single file installer that will work as both a clean
install and an update to previous installs. The catch is that in update
mode I need to change an existing component, add a new component, and
leave a third in
4 matches
Mail list logo