From: SourceForge.net <no...@so...> - 2005-07-16 21:54:22
|
Bugs item #1229152, was opened at 2005-06-28 09:28 Message generated for change (Settings changed) made by robmen You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=642714&aid=1229152&group_id=105970 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: light Group: None >Status: Closed Resolution: Fixed Priority: 5 Submitted By: Brian Simoneau (briansimoneau) Assigned to: Rob Mensching (robmen) Summary: Properties within conditions are not propety modularized Initial Comment: I have a merge module that contains something like <ScheduleReboot After="ProjectSuccess">PropertyA = "1" AND PropertyB = "1"</ScheduleReboot> within the <InstallExecuteSequence>. When I add the merge module to another msi, only PropertyA is modularized. Looking at the InstallExecuteSequence table for the parent msi in Orca, the Condition column has PropertyA.GUID AND PropertyB I believe that PropertyB should also be modularized with the .GUID extension from the merge module. Switching the order of PropertyA and PropertyB makes the Condition look like PropertyB.GUID AND PropertyA. The first property listed in the condition is the only one that is correct. ---------------------------------------------------------------------- Comment By: Rob Mensching (robmen) Date: 2005-07-05 18:58 Message: Logged In: YES user_id=991639 Conditions are not modularized correctly right now. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=642714&aid=1229152&group_id=105970 |