I would recommend: - Using RegistrySearch to read the existing values of registry values; - Using the RegistryValue element to set new values, using property substitutions to construct the value (the Value attribute is a Formatted data type, so you can use [PropertyName] to substitute the PropertyName property's value); - Using property-type custom actions <CustomAction Property="Name" Value="expression"/> to set the property value to be written to the key; - If you need to manipulate the value read from the registry further, writing a C++ custom action that simply performs the manipulation.
Doing it through MSI tables should ensure that Windows Installer correctly detects when a repair is needed. It also means that the registry changes are transactional, i.e. rolled back if there's a problem with the installer. I suspect you're just trying to reuse code that manipulates these registry entries, written for setting them up properly when debugging from the IDE. It's nice to have code reuse. Writing your installer properly should be a higher priority, however. If you must do it in the debugging environment, come up with a way that the debugged code can read the WiX source and make that the master source of the registry information. -- Mike Dimmick -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Sanin Sent: 30 March 2008 00:12 To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Re compiling WiX C++ libs for 64-bit LOL Just writing registry keys, of course, is not the only thing that happens inside .NET custom actions. Sometimes we have to read a registry key already written and perform a certain action, or write a new key whose value is not that easily derived to be handled by the Registry table. Bob Arnson-6 wrote: > > Sanin wrote: >> 2. Explicitly pass appropriate flag when using registry classes from .NET >> so >> that automatic redirection does not happen. >> > > Why would you go through the hassle of writing a C++ custom action that > loads a .NET assembly to write to the registry when MSI already supports > 64-bit registry paths via the Registry table? > > -- > sig://boB > http://joyofsetup.com/ > > > > ------------------------------------------------------------------------- > Check out the new SourceForge.net Marketplace. > It's the best place to buy or sell services for > just about anything Open Source. > http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace > _______________________________________________ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > > -- View this message in context: http://www.nabble.com/Recompiling-WiX-C%2B%2B-libs-for-64-bit-tp16261155p163 76741.html Sent from the wix-users mailing list archive at Nabble.com. ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
