Hi, You can condition the component which is associated with xml change. Have the condition 'Not Installed' as the condition so it runs first time only.
You could also add a condition to the ISXml... custom actions, but it can be a bit tricky, as you need to understand exactly what each of them is actually doing.
Another alternative would consist in isolating your component in a separate feature, and configure it so that the feature itself does not get reinstalled in your upgrade scenario. Indeed, the XML file changes are only applied to components when the corresponding feature gets (re)installed. But depending on your feature configuration, you might not be able to isolate the component.
Alternatively, you can leave the XML file changes as they are, but add a system search to your project, which looks for the information in the XML file you are configuring at installation.
In an upgrade scenario: [LIST=1]
The information will be read from the XML file thanks to the system search.
The XML File changes will apply the changes to this XML file again.
As a result, your XML file will remain unchanged after an upgrade.
Hi again, I moved my XML config to it's own seperate feature and set the condition of the Feature to not reinstall in the upgrade scenario as suggested. This seems to have worked!
