The __Components are MSI things (for costing, IIRC). You can ignore them. The registry key path/name/value should not be case sensitive but whenever referring to an Id in the MSI you should assume that it is case sensitive (because it almost always is).
-----Original Message----- From: Chris Ridd [mailto:chrisr...@mac.com] Sent: Friday, February 06, 2009 05:50 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Control conditional on installed components On 5 Feb 2009, at 18:36, Rob Mensching wrote: > You need the "*v" to get it all. I never bother with logs any other > way. Nothing else (except the MSI itself to cross reference) is > usually necessary. OK, I now have verbose logs of an install with Java and without Java. I'm eliding all the variants for other JREs and JDKs, and everything that follows is in the order stated. In the "with Java" case I see: MSI (s) (D8:0C) [13:20:06:562]: Component: FOO_JDK15; Installed: Absent; Request: Local; Action: Local ... MSI (s) (D8:0C) [13:20:06:562]: Component: FOO_NOJAVA; Installed: Absent; Request: Local; Action: Null ... MSI (s) (D8:0C) [13:20:06:562]: Component: __FOO_JDK1565; Installed: Null; Request: Local; Action: Local ... MSI (s) (D8:0C) [13:20:06:562]: Component: __FOO_NOJAVA65; Installed: Null; Request: Local; Action: Null ... MSI (s) (D8:0C) [13:20:10:375]: Executing op: ComponentRegister (ComponentId ={B72D1D96-4E3E-4A86-7406-80BAAD4F6774},KeyPath=02:\Software\foo\foo \14.4\Foo_JDK15\,State=3,,Disk=1,SharedDllRefCount=0,BinaryType=0) ... MSI (s) (D8:0C) [13:20:24:515]: Executing op: RegOpenKey(Root=-2147483646,Key=Software\foo\foo \14.4\Foo_JDK15,,BinaryType=0) MSI (s) (D8:0C) [13:20:24:515]: Executing op: RegAddValue(,,) WriteRegistryValues: Key: \Software\foo\foo\14.4\Foo_JDK15, Name: , Value: ... MSI (c) (74:D4) [13:20:25:328]: Doing action: MyExitDialog In the "without Java" case I see: MSI (s) (D8:24) [13:22:27:640]: Component: FOO_JDK15; Installed: Absent; Request: Local; Action: Null ... MSI (s) (D8:24) [13:22:27:640]: Component: FOO_NOJAVA; Installed: Absent; Request: Local; Action: Local ... MSI (s) (D8:24) [13:22:27:640]: Component: __FOO_JDK1565; Installed: Null; Request: Local; Action: Null ... MSI (s) (D8:24) [13:22:27:640]: Component: __FOO_NOJAVA65; Installed: Null; Request: Local; Action: Local ... MSI (s) (D8:24) [13:22:30:281]: Executing op: ComponentRegister (ComponentId ={452BBD08-4BA3-4217-4C4D-016F4E2E56B6},KeyPath=02:\Software\foo\foo \14.4\FOO_NOJAVA\,State=3,,Disk=1,SharedDllRefCount=0,BinaryType=0) 1: {17D464B1-EA8F-42DD-A89D-F1D0D2101DDB} 2: {452BBD08-4BA3-4217-4C4D-016F4E2E56B6} 3: 02:\Software\foo\foo \14.4\FOO_NOJAVA\ ... MSI (s) (D8:24) [13:22:35:890]: Executing op: RegOpenKey(Root=-2147483646,Key=Software\foo\foo \14.4\FOO_NOJAVA,,BinaryType=0) MSI (s) (D8:24) [13:22:35:890]: Executing op: RegAddValue(,,) WriteRegistryValues: Key: \Software\foo\foo\14.4\FOO_NOJAVA, Name: , Value: ... MSI (c) (C0:28) [13:22:40:640]: Doing action: MyExitDialog So it certainly looks like it is installing the right FOO_* component each time, and the right HKLM\Software\foo\foo\14.4\Foo_* key created each time (I verified this using regedit as well). The "__FOO_*65" components are not AFAIK created by me. Where are they coming from? Apart from those components, it is logging what I was anticipating. Any suggestions on what to search for in the logs? Are component names and registry keys case-sensitive? Cheers, Chris ------------------------------------------------------------------------------ Create and Deploy Rich Internet Apps outside the browser with Adobe(R)AIR(TM) software. With Adobe AIR, Ajax developers can use existing skills and code to build responsive, highly engaging applications that combine the power of local resources and data with the reach of the web. Download the Adobe AIR SDK and Ajax docs to start building applications today-http://p.sf.net/sfu/adobe-com _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------------ Create and Deploy Rich Internet Apps outside the browser with Adobe(R)AIR(TM) software. With Adobe AIR, Ajax developers can use existing skills and code to build responsive, highly engaging applications that combine the power of local resources and data with the reach of the web. Download the Adobe AIR SDK and Ajax docs to start building applications today-http://p.sf.net/sfu/adobe-com _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users