Hi all, I finally took the plunge, downloaded WiX 3.5 (the Dec 30th edition), installed it, and even read some of the documentation.
What I would like to achieve: Create a setup for one of the projects in our main solution file and have the .msi built as part of our TFS build. One of the topics in the help file I stumbled across was the VS "create your first setup" topic. Simple enough: add a reference to my CS project. This neatly avoids me having to figure out what paths to specify. Which can be painful, seeing as the paths on our TFS server tends to be a bit different. In our present InstallAware-based solution we tend to use environment variables a lot. The downside to heat.exe is that it refuses to scan my project's assembly references. I end up having to add references to a bunch of different assemblies, and then eventually to some third-party assemblies which may be in locations that tend to vary a bit between our build server and developer workstations. Is the idea that I can use heat.exe to get a reasonable starting point from which I can manually add files as needed? Or is heat.exe supposed to dig a bit deeper in the references section of my CS project and add the referenced assemblies directly? Could someone please show me the right tree to bark up? TIA. -- Rune ------------------------------------------------------------------------------ Protect Your Site and Customers from Malware Attacks Learn about various malware tactics and how to avoid them. Understand malware threats, the impact they can have on your business, and how you can protect your company and customers by using code signing. http://p.sf.net/sfu/oracle-sfdevnl _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
