I'm working on an installer project that has a mix of legacy VB applications and .NET applications.
Originally, I exposed /dark /to an existing MSI, but I wasn't happy with the output. So I thought I'd give /heat/ a try; I used /heat /to melt the old VB apps down to wxs files and I can sort of see where all that's heading with all the various fragments and component groups. Then I noticed that my WiX project has references to all the .NET projects that I'd like to install and I don't recall adding the references. Is this something that /dark /did? Or is this a consequence of having my WiX project part of a solution with all the other .NET projetcts? Is this something that is required for installing .NET applications? Should I be using /heat/ to melt the bin\Release of my .NET projects? Or is there a better/easier method? Where can I get detailed info on all the Extensions (WixNetFxExtension, WixUIExtension, et. al.)? Thanks, Bill ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
