Corner Geoff wrote: > > The way to go with WiX seems to be to create an overall wxs file and > have a sub file for each component, >
In the tutorial, it says: "In general, you should restrict yourself to a single file per component" What this means is that you (in general) should only have one of your files per installer component, so you typically put exe, .dll, .ocx, .chm, or .hlp files in separate components. The final msi will look the same if you have one or thirty WIX files with one component each. As one that is currently making the transition from Installshield to WIX, I would recommend the book "WiX: A Developer's Guide to Windows Installer XML" (you can get it as an eBook). https://www.packtpub.com/wix-developers-guide-windows-installer-xml/book -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/A-question-from-a-complete-Newbie-tp6835282p6836805.html Sent from the wix-users mailing list archive at Nabble.com. ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2dcopy1 _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
