dB. wrote: > My product has a configuration file. We want it to stay on the machine > when the product is uninstalled since the user might have changed it. We > copy configuration files at installation time in a very nicely > implemented custom action that copies files outside of component > rules... I've just discovered a component attribute Permanent=no that > seems to accomplish the same thing (I can put my file in a separate > component and mark it permanent). > > > > Should I scrap my CAs? Are there reasons not to use Permanent=yes? >
Well, it leaves behind parts of your product, normally not a good result. But if you were doing that anyway, sure, no harm. Though generally, a per-machine install would write the default settings to a per-machine location and the user would modify a local copy created at first run. FWIW... -- sig://boB http://joyofsetup.com/ ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
