| Could you instead write that registry value in its own component
| after computing it based on the installation states of the other
| components that need to contribute to it?
Hi Blair,
I think I'll go that way...I even tried to use SetProperty each time a
component is processed, to build the final string and write to registry
only once, but an ICE validation complained about the duplicate action.
Can I do this in an iterative fashion instead of a bunch of conditions?
André Felipe Werlang
Antes de imprimir pense em seu compromisso com o Meio Ambiente
e o comprometimento com os Custos
-----Mensagem original-----
De: Blair [mailto:os...@live.com]
Enviada em: 3 de setembro de 2009 19:25
Para: 'General discussion for Windows Installer XML toolset.'
Assunto: Re: [WiX-users] Is it possible to read registry during execution?
Not without replacing the WriteRegistryValues built-in action. Even then it
would be a severe violation of the component rules.
What happens is that the costing actions determine which components will be
installed. Each of the other actions then reference the action state of each
component referenced in their respective tables and then "blasts" those values
out to the respective locations. The only built-in support for registry value
concatenation is for multi-string registry values where each appended string is
an additional string in the value, not a concatenation on any existing string.
Could you instead write that registry value in its own component after
computing it based on the installation states of the other components that need
to contribute to it?
-----Original Message-----
From: André Werlang [mailto:and...@gvdasa.com.br]
Sent: Thursday, September 03, 2009 1:09 PM
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] Is it possible to read registry during execution?
Hi!
I have a dozen components such that for each it can be written on registry
the same key entry, concatenating with the old value.
But, I've just found that RegistrySearch is made during AppSearch, which happens
to be the first action in execute sequence, so my approach didn't work.
Can it be made that the reading is accomplished just before it is written again?
Thanks
André Felipe Werlang
Antes de imprimir pense em seu compromisso com o Meio Ambiente
e o comprometimento com os Custos
------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
