I'd say it differently:
1. Static configuration should go in the install. That way repair will do the
right thing.
2. Defaults for configuration should go in the app directly (a static
configuration file) or in the install. That way repair will do the right thing.
(the above two things are ideally 100% "per-machine" settings)
3. Dynamic configuration (stuff that you expect the user to change, aka
per-user) should be updated using a configuration tool (or just the app itself,
Tools -> Options...). Ideally, per-user configuration is only be written when
it differs from the defaults.
So it goes like this:
static in the install, dynamic not in the install.
Now, the part that really gets hard is when you do an upgrade and previous
settings need to be migrated/upgraded/or otherwise modified. IMHO, first boot
of the new application is the ideal place to do this.
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Aaron Feng
Sent: Monday, June 04, 2007 7:40 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] External configuration vs CustomActions
I just wrote a post on external configuration vs CustomActions. I would like
to get general feedback on this particular topic. If you are interested, the
link is here:
http://aaronfeng.com/articles/2007/06/04/how-should-your-application-be-configured
Thanx in advance.
Aaron
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
