[WiX-users] question mark instead of colon in components registry keys

What causes the paths inHKLM\Software\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Components to contain question marks instead of colons? For example, I find paths that look like this: C?\Program Files\Common Files\Microsoft Shared\VBA\VBA6\VBACV10.DLL instead of

Re: [WiX-users] question mark instead of colon in components registry keys

Mike Gallaway wrote: What causes the paths inHKLM\Software\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Components to contain question marks instead of colons? Short answer: It doesn't matter. That's data maintained by MSI, so as long as it's happy with what it

[WiX-users] Bug with tallow in registry parsing?

Hi, I just noticed what I believe is a bug with tallow, when using tallow reg somefile.reg and the regfile contains a empty string, for instance Example1=, tallow generates a Value= corresponding to the value, this however generates a error CNDL0006 : The Registry/@Value attribute's

Re: [WiX-users] Extract files from msi (Msiexec, not WIX issue... .)

While secretly conversing with Derek I have managed to fix my original issue. After running MSI validation from Orca I found a strange error relating to the windows and system folder components... They had no parent! It seems that WIX allowed it to go through and it does in fact copy the

Re: [WiX-users] Sequencing issue

Totally - I want to get it to run before then so it can roll back but can't seem to write the file to make it work anywhere else Ed Ed Russell CME Product Development Manager Co-operative IT t: +44 (0) 845 458 5007 m: +44 (0) 7976 055 504 f: +44 (0) 1527 880 975

Re: [WiX-users] Sequencing issue

Are the files GACed assemblies or just normal files? If they are normal files then you can just schedule your CA after InstallFiles. What does your CA do? Derek -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Ed Russell Sent: Wednesday, June 14, 2006

Re: [WiX-users] Registry key or value localization problem

I think I narrowed down the problem I'm seeing.  The code below works from a Product/ WiX file but not from a merge Module/ WiX file. Component Id='AppFRA' Guid='73EF5301-BEEC-40b0-9A38-5AB812C1897D' Registry Id='ReceiveProtocolsFRA' Action='write' Root='HKLM'    

Re: [WiX-users] Registry key or value localization problem

That looks fine to me have you tried just performing the install to see if it works?  Sometimes Orca has problems with different languages but that doesnt necessarily mean the msi itself is wrong.  Be sure to merge the module into an msi with the proper codepage set as well. (please