I remember reading that one of the stated aims is to get setup into the main build process, so that you develop the program and setup simultaneously.
I've got two separate sets of outputs from my project, a demo and a retail version, and I want a separate version of the installer for each. So, I have my base project that builds an exe, say mainprog.exe I also might have some custom actions I build (but don't yet). After those are built, I want to build my msi file for the relevant configuration. Alas, this is where my problems start. First of all, it doesn't seem possible to add a dependency on the output of a separate project. Maybe this isn't possible at all, but it seems there must be some workaround. The file I want to bundle into my msi is either $(Solution)\demo\mainprog.exe or $(Solution)\retail\mainprog.exe If in the demo config mainprog.exe is newer than my output, I want to rebuild my wix project. Ditto in the retail comfig. I've thought about making a makefile project, but I can't seem to figure this out either. There doesn't seem to be any way to set the custom build step. Could anyone give me some pointers as to where to start looking? Anthony Wieser Wieser Software Ltd ------------------------------------------------------------------------- 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
