I do not really know the answer to your latest questions. In a wix context I think I would use the Wix:MsuPackage and let it handle those details (but I have not had the ocassion to do that yet). I have previously installed msu packages in a non-wix setup using wusa.exe "package-name.msu" /quiet /norestart
I was aware that the actual install packages could be extracted from the msu, and that there is an xml file, but I just used the wusa.exe tool rather than going that route. Given that there is a Wix designed feature for this I would try to make use of that feature. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/MSU-raw-cab-tp7593094p7593099.html Sent from the wix-users mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Subversion Kills Productivity. Get off Subversion & Make the Move to Perforce. With Perforce, you get hassle-free workflows. Merge that actually works. Faster operations. Version large binaries. Built-in WAN optimization and the freedom to use Git, Perforce or both. Make the move to Perforce. http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk _______________________________________________ WiX-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wix-users
