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

2007-03-02 Thread Bob Arnson
Tobias Bengtsson wrote: > that makes sense.. how do one go about to use explicit AddLocal controls? > can't recall to have seen the use of it in the great tutorial by Gabór. > I don't see any examples in the WiX tree. The basic idea is that you have a control event tied to a button (e.g., Nex

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

2007-03-01 Thread Tobias Bengtsson
obias 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): POSSERVER = "1"

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

2007-03-01 Thread Bob Arnson
Tobias Bengtsson wrote: They are like this (from the top of my head): POSSERVER = "1" Using feature conditions like that isn't going to work. The problem is that the UI sequence sets an explicit list of which features get added or removed so feature conditions that rely on

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

2007-03-01 Thread Tobias Bengtsson
iX-users] Properties read in with RegistrySearch, manipulated after that in the UI Tobias Bengtsson wrote: I am experiencing the same behavior on the installer as I did before.. the components with a conditional install (e.g. POSSERVER="1") get's installed the second time I

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

2007-02-28 Thread Bob Arnson
Tobias Bengtsson wrote: I am experiencing the same behavior on the installer as I did before.. the components with a conditional install (e.g. POSSERVER="1") get's installed the second time I run the installer, and the Registry values which gets read in by AppSearch, exists.. What are you