Re: [WiX-users] Properties read in with RegistrySearch, manipulated after that in the UI

/Condition /Feature Tobbe From: Bob Arnson [mailto:[EMAIL PROTECTED] Sent: den 28 februari 2007 17:58 To: Tobias Bengtsson Cc: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Properties read in with RegistrySearch, manipulated after that in the UI Tobias Bengtsson wrote: I am

Re: [WiX-users] Properties read in with RegistrySearch, manipulated after that in the UI

Bengtsson Kopia: wix-users@lists.sourceforge.net Ämne: Re: [WiX-users] Properties read in with RegistrySearch, manipulated after that in the UI Tobias Bengtsson wrote: They are like this (from the top of my head): Feature Id=Feature1etc... Level=3 ComponentRef Id

[WiX-users] Propertys read in with RegistrySearch, manipulated after that in the UI

Hey everyone, Which action evaluates which features to be installed? In my different features I use conditions to decide what to be installed or not (Condition Level=1NAME = test/Condition, installed If NAME=test), and depending on if the property gets set with a RegistrySearch or in my own

Re: [WiX-users] Propertys read in with RegistrySearch, manipulated after that in the UI

Thanks bob, I understand how to make them secure, but how do one make a property public? Regards, Tobias From: Bob Arnson [mailto:[EMAIL PROTECTED] Sent: den 26 februari 2007 17:03 To: Tobias Bengtsson Cc: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Propertys read

[WiX-users] Create a LocalGroup in the installation

VBScript out of this... Anyone got a different idea on how to accomplish this? Regards Tobias Bengtsson - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get

[WiX-users] Duplicate registry entries (in separate feautures) in the same project..

or have a different installer that sets this on top of the main installation. Regards, Tobias Bengtsson - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share

[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