I'm new to MSBuild (and WiX for that matter) and I've been trying to figure out
how to use the wix.targets definitions to set up the installer project for my
.NET solution. The four project output types that come with the Votive Visual
Studio templates work fine, but what I'd like to be able to do is build my
single installer project from WiX source to executable package, which would
require building the MSI as an intermediate step. From what I can tell, it
doesn't look like this is possible with the definitions in the wix.targets file
because it would require more than one pass through the compilation and linking
steps and distinguishing between the files that are part of the product and
those that are part of the bundle. I wanted to check if my conclusion was
accurate and get advice about how I should set up the installer project(s) in
my solution. Should I have separate projects for the MSI and the executable,
or should I just write my own .wixproj that makes use of the WixTasks.dll?
The application suite I'm working on will require building two installers, one
of which will mostly just contain a subset of components from the other. Given
that there will be a lot of fragments in common between the two, what is the
best recommendation for configuring my projects? I originally didn't think
I'd need multiple projects within my solution to handle the installers but I'm
not so sure anymore. Any guidance would be appreciated.
------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_jan
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
