I never undestood why MSI doesn't have this automatic state saver pattern built
in.
BTW a better approach is to read the results of AppSearch into another set of
properties and assign the primary properties only if they are null. This
allows you to service repairs and upgrades with override values. The goal
is to make sure full ui, silent installs, installs, uprades, elevated installs
all behave the way you expect them to.
Richard <[EMAIL PROTECTED]> wrote:
In article <[EMAIL PROTECTED]>,
"dB." writes:
> How can I preserve the values between install and uninstall?
Write the property into the registry on install and use AppSearch to
scrape it out of the registry. This will reconstitute the property
value on modify, repair and uninstall -- basically any interaction with
your package after its installed.
--
"The Direct3D Graphics Pipeline" -- DirectX 9 draft available for download
Legalize Adulthood!
-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
---------------------------------
Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now.-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
