Hi, I'm using WiX 3.0 and am looking for some advice on the best way to setup an install package for a project I am working on. I've previously built a setup that will create a database on a SQL Server and then run a script to create tables, stored procedures, etc. What I would like to do now is to be able to update the database (e.g. modify table definitions, create new stored procedures, change existing ones, etc) when I have a new version. I know that I can make the changes using SQL scripts. What I am wondering is what is the best way to set this up in WiX?
Can I have a single install package that will create the database if the product has not been installed previously but will only update the database (execute the update scripts) if it already exists? Should I maintain two packages - one for a fresh install and one for updates? What about in the third and subsequent versions? Can I get the install program to run the updates for version 1.0.0 --> version 1.0.1 and then version 1.0.1 --> version 1.0.2? Should I just create a standalone executable to manage the database updates? Any thoughts or references would be appreciated. Tom ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
