Hello all, I want to know if there are any guidelines (best practices) to care about before clubbing 2 MSI s together using burn. For e.g. I have m1 and m2 as two msi s.
Both the msi have their own LaunchConditions (which may overlap) where they check before install (like .NET framework version, OS version etc.). Then they start with their installation. Besides, I have doubt about UI integration. Like, m1 individual install is like a very simple msi install (just click next .. next) while m2 has feature selection kind of UI (typical, custom, full) and then you go next .. next. So, in what way should I club the UI experience in Burn or there is no need to ? -Vivek -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Using-Burn-to-club-2-msi-s-initial-doubts-tp7580493.html Sent from the wix-users mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
