Yes, I want a single unified installation. The flow of UI would be something like:
1- Welcome 2- Ask for user inputs (checkbox, filling some values) 3- The user inputs can now be passed to m1 and m2 if they need that specific info 4- m1 runs with its input 5- m2 runs with its input 6- finish I wrote steps 4 ,5 individual because I think then I can reuse most the old msi code , okay ? I guess the main challenge for me it to create a unified UI for the both msi (newbie). Once I have the individual params for the individual msi, I can run msiexec one after the other. How does this approach sounds ? -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Using-Burn-to-club-2-msi-s-initial-doubts-tp7580493p7580544.html Sent from the wix-users mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Got visibility? Most devs has no idea what their production app looks like. Find out how fast your code is with AppDynamics Lite. http://ad.doubleclick.net/clk;262219671;13503038;y? http://info.appdynamics.com/FreeJavaPerformanceDownload.html _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
