How do I use WIX to prevent overwriting a config file during a ‘Major Upgrade’?
I want the file to be installed on the initial install, removed on uninstall, and left unchanged on a ‘Major Upgrade’.
Thanks
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
How do I use WIX to prevent overwriting a config file during a ‘Major Upgrade’?
I want the file to be installed on the initial install, removed on uninstall, and left unchanged on a ‘Major Upgrade’.
Thanks
The most straight forward way would be to schedule your RemoveExistingProducts after InstallExecute or InstallFinalize. That way the config file is not removed and then installed again (like if you schedule before InstallInitialize). Of course, scheduling RemoveExistingProduct so late means you need to be very careful about your Component Rules.
My personal favorite is to treat configuration like ‘user data’ and not have the installtouch it at all. You ship defaults with the application but any changes are made by the user in their private user profile. Gets you out of all kinds of nasty migration problems that just aren’t solved well during setup.