BhaveshG wrote:
> I was able to figure the syntax and execute but this is works only for
> install and uninstall. It does not have a repair option and hence the files
> do get overwritten with the XML stuff:(
>
In WiX v3, you can override the conditions on custom actions but that's
not availab
I was able to figure the syntax and execute but this is works only for
install and uninstall. It does not have a repair option and hence the files
do get overwritten with the XML stuff:(
Bhavesh
BhaveshG wrote:
>
> Thanks Bob.
>
> Please do let me know the XmlConfig syntax.
>
> Currently i
Thanks Bob.
Please do let me know the XmlConfig syntax.
Currently in my files the values I have set during first-install are
overwritten in "Repair" mode with blank values. I would not like to execute
the XMLFile statements again in repair mode.
Bhavesh
Bob Arnson-6 wrote:
>
> BhaveshG wro
BhaveshG wrote:
> I cannot use XmlConfig as I need to update value for the XML elements and
> XmlConfig I guess only has create and delete options.
>
XmlConfig is a superset of XmlFile functionality. You'll have to author
it different but should be able to do everything XmlFile supports with
Thanks for your reply.
I cannot use XmlConfig as I need to update value for the XML elements and
XmlConfig I guess only has create and delete options.
The other option which I thought and used while repair was to set the
condition for the component by having transitive to yes and then checking
f
BhaveshG wrote:
> 1. Typically when you do a repair only the files that are missing or corrupt
> are deployed which happens to me as well. But even for the existing file
> XMLFile statement is executed and my files are updated on "Repair". The
> XMLFile tag does not accept any "Condition" text as t
6 matches
Mail list logo
