Presumably, I need to set up a second completely separate edit to achieve this.
mihai.petcu wrote:This is correct. As each .XML edit is associated with a component, to condition the .XML edit for a certain component, you would have to create a new .XML edit associated with that component.
mihai.petcu wrote:If this doesn't work you can try to add a formatted reference to a public property in the same .XML edit whose value will be set conditioned by the selected component. You can achieve this with the help of "SetProperty" conditioned published events or "Property Set with Formatted" custom actions.
mihai.petcu wrote:This is the actual intended functionality of the associated .XML file to a component. If the component is not modified, its associated .XML file won't be as well.
mihai.petcu wrote: To avoid the duplicate error, you can have your second .XML update placed in a subfolder with the "Install folder content into the parent folder" option enabled( can be set from the "Properties..." context menu ).
PhilB wrote:I do not have this option selected in either of my two edits yet the backup file is still produced for the case where both edits are required.
Users browsing this forum: Bing [Bot], Google [Bot], InnovRick and 10 guests