Bugs item #1833513, was opened at 2007-11-16 19:34 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=642714&aid=1833513&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: v3.0 Status: Open Resolution: None Priority: 5 Private: No Submitted By: Heath Stewart (heaths) Assigned to: Nobody/Anonymous (nobody) Summary: 32- and 64-bit components generate same GUID Initial Comment: If a component is using a registry key path under the current rules for automatically generating GUIDs, the bitness of the component is not taken into account. The result is a shared component that has the same key path, but actually installs to separate registry keys - either the intended hive, or the WOW key under the intended hive. These should have separate component GUIDs, thus the binder should account for the bitness of a component. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=642714&aid=1833513&group_id=105970 ------------------------------------------------------------------------- SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 _______________________________________________ WiX-devs mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wix-devs
