I concur with John's post. I make sure all projects can be built using scripts that call MSBuild and VS. I avoid using VS events (PostBuild) in favour of BeforeBuild and AfterBuild nearly every project. There are other helpful MSBuild targets which can be reviewed by enabling a verbose build log.
I also had build dependency problems using a wixlib in projects where I was also using a single wix setup project to build both a x86 and x64 output in two passes. The wixlib and the x86 project would build successfully, then MSBuild would try to build the wixlib again using a Platform=x64 (in order to build the x64 project), and fail. VS built OK but building on the command line using msbuild was important for me, so I removed wixlibs from those projects. If the wixlib related code is only wxs, like in the CommonLib project of the Wix toolset source Setup, projects, then I prefer to put that code in my compiler extension wixlib, which is called for every project anyway. If the code is common to many, but not all, projects, changes rarely, may need preprocessing, I put it in a 'common' area, and use batch scripts to copy it to all of the affected projects. If I don't have any build issues using either VS or MSBuild when using a wixlib, then I don't need to do any of the above. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Build-order-problems-Votive-vs-MSBuild-tp7594932p7595540.html Sent from the wix-users mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Open source business process management suite built on Java and Eclipse Turn processes into business applications with Bonita BPM Community Edition Quickly connect people, data, and systems into organized workflows Winner of BOSSIE, CODIE, OW2 and Gartner awards http://p.sf.net/sfu/Bonitasoft _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
