Advanced installer - dealing with svn conflicts
<p>I am trying to find out what is the best way of dealing with conflicts in advanced installer projects.</p>

<p><strong>Problem:</strong> If I modify even single field (e.g. Install Condition for IIS web site) after saving project I see that almost whole file changed and these changes are way too confusing (some entries reordered/removed or just slightly modified e.g. just NextFile property changed).</p>

<p>I have few options:</p>

<ol>
<li>Documenting all steps in UI required to perform the change and commit confusing changes in installer (and then when merging just change things from in UI)</li>
<li>After changing installer from UI revert all confusing changes and leave only those changes which reflect what I actually changed through UI (e.g. if I changed just Condition in UI then ONLY that condition should be changed in XML)</li>
</ol>

<p>2) sounds better to me as I'd like to have clear history in SVN, however sometimes it will be very difficult to find out what is required and what should be reverted. </p>

<p>Ideally I'd like advanced installer to change only that what I have changed. If that is not possible can anyone please explain me what is the right process of dealing with advanced installer changes across multiple branches? </p>

<p>(Advanced Installer 10.3)</p>