Hi all -- we have a bundle containing MsiPackage entries for SQL Server Compact 3.5 SP2. There are actually two MSI's: x86 and x64. The latter seems to have problems being repaired via our bootstrapper (standard burn bootstrapper application, no custom code). I don't want to further hijack another thread (smile), so I'll just start a new one.
Both MSI's are marked 'visible' and 'permanent', so the user can choose to repair them via the Control Panel if they wish. I'd like to find out if there is a way to declaratively tell burn not to repair these two MSI's: just leave them alone. Thanks for any advice ! -Rob -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/How-to-prevent-repair-of-permanent-MsiPackage-tp7596617.html Sent from the wix-users mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Slashdot TV. Video for Nerds. Stuff that matters. http://tv.slashdot.org/ _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
