This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- InstallShield
- :
- InstallShield Forum
- :
- XML File Changes condition
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Sep 06, 2013
02:45 PM
XML File Changes condition
I have a simple XML File Change that creates a small XML file containing a single datum based on the value entered in a text field. That part works wonderfully.
However, on update I have no desire to overwrite or touch that file. So I have a system search that sets a property if the file exists, and the component corresponding to the XML File Change has a condition of Not (that property).
It was my expectation that by assigning a condition to the component corresponding to an XML File Change, if that condition evaluates to false the XML File Change will not be performed, and the dialog with the text field will not be shown. When the search discovers the file, the dialog is not shown, however the XML File Change is performed. This is the case whether I depend on the system search result property, or I put in a statically false condition that will never evaluate to true.
Is this not a correct expectation?
Currently my workaround is just to read that datum back in via an Xml value system search so that the file is written out correctly again, but that's less than optimal. I have other Xml file changes, so restricting the entire CA is not an option. Why does the component condition being false not prevent the XML File Change from occurring? If that is by design, what purpose does having the component serve?
However, on update I have no desire to overwrite or touch that file. So I have a system search that sets a property if the file exists, and the component corresponding to the XML File Change has a condition of Not (that property).
It was my expectation that by assigning a condition to the component corresponding to an XML File Change, if that condition evaluates to false the XML File Change will not be performed, and the dialog with the text field will not be shown. When the search discovers the file, the dialog is not shown, however the XML File Change is performed. This is the case whether I depend on the system search result property, or I put in a statically false condition that will never evaluate to true.
Is this not a correct expectation?
Currently my workaround is just to read that datum back in via an Xml value system search so that the file is written out correctly again, but that's less than optimal. I have other Xml file changes, so restricting the entire CA is not an option. Why does the component condition being false not prevent the XML File Change from occurring? If that is by design, what purpose does having the component serve?
(1) Reply
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Dec 03, 2013
03:03 PM
Hi Troy,
There are a couple of considerations in regards to your issue.
If you look in the XML File Changes view under the Installation Designer tab (in InstallShield) under the general tab, the XML file change is tied to a feature as well. Try looking at the feature condition to see if this is the cause.
A verbose log file would help to determine what is causing the sml file change to occur.
http://kb.flexerasoftware.com/selfservice/viewContent.do?externalId=Q104807
You may need to have an invisible feature for this XML file change to have its own condition.
A different look. You could use a custom action that if the file exists to copy the file out and then another custom action to copy the file back once install has finished.
Kind Regards,
Grant
Flexera Software Technical Support
There are a couple of considerations in regards to your issue.
If you look in the XML File Changes view under the Installation Designer tab (in InstallShield) under the general tab, the XML file change is tied to a feature as well. Try looking at the feature condition to see if this is the cause.
A verbose log file would help to determine what is causing the sml file change to occur.
http://kb.flexerasoftware.com/selfservice/viewContent.do?externalId=Q104807
You may need to have an invisible feature for this XML file change to have its own condition.
A different look. You could use a custom action that if the file exists to copy the file out and then another custom action to copy the file back once install has finished.
Kind Regards,
Grant
Flexera Software Technical Support