I'm not clear on the best practice for packaging up large groups of files,
such as a website. I understand that the wix file needs to have each file
individually listed. But how do you achieve this practically, especially
with a website? Adding the installer project to the website solution and
then asking developers to keep the installer's file listing up to date
manually seems very error prone. It seems very likely that files will not
get added and the addition will not be missed until we're testing in QA.
I'm looking for a more solid approach that keeps the installer in sync with
the source projects its associated to. Visual Studio deployment projects
(vdproj) allow you to capture all output from a specific project. Are there
any wix plug-ins for VS that do the same thing? I've also read that some
people generate their wix files at build time using scripts. I could do
this, but I'm a bit concerned about the added complexity to my build system
(it would be less obvious to new developers how certain files got picked up
by the installer).
Any insights on best practices would be appreciated.
Christopher
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
