On 16-May-14 20:23, Sean Hall wrote: > I thought the goal was to be able to compile your existing project on > the next version and everything work like before. There could be > someone who set their .NET package InstallCondition to "0 = 1", and > then it would be different.
We reserve the right to laugh at people doing silly things. Is that a silly thing? Seems like it. I can see it as an attempt to prevent repair but obviously removing @RepairCommand is better. If it's not silly, then we need a "force" option. My previous comments were to indicate that we should use the same mechanism to support all the pre-req packages rather than treating WixMbaPrereqPackageId differently than the support packages. -- sig://boB http://joyofsetup.com/ ------------------------------------------------------------------------------ "Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE Instantly run your Selenium tests across 300+ browser/OS combos. Get unparalleled scalability from the best Selenium testing platform available Simple to use. Nothing to install. Get started now for free." http://p.sf.net/sfu/SauceLabs _______________________________________________ WiX-devs mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wix-devs
