Jun 18, 2008 For example, you may see. Open XML diff tools. OpenXmlDiff uses the XML Diff and Patch Utility (a free download on MSDN). .NET XML Power Tools Using the XML Diff and Patch Tool in Your. The XML Diff and Patch GUI Tool. For example), whereas an XML fragment could be any set of XML.
At this moment, I am managing a piece of software that has multiple XML configuration files. When a new version of software is released, sometimes the base config files change, we currently have the software call on startup. If it detects a change, it prompts the user to choose the changes. The problem with this approach is that KDiff is a line comparing program and not aware of the ways of XML (like Nodes, etc.) Ideally, I would like to programmatically work with a library in C# (since we're a MS shop) that can Diff two XML files: a Source XML and a Current Working XML. And then Merge the two together using a few simple rules:. If the Current Working XML has a node that the Source XML does not, remove it. If the Source XML has a node that the Current Working XML does not, add it. Callen ultrasonography in obstetrics and gynecology 6th edition.
Give More Feedback
If both have the same node and the values differ, favor the Source XML's value, unless it the Source XML's value is set to 'UseExistingValue'. For example, here's the 'Source' XML: And here's the 'Current Working' XML: And the merged version would look like: I've looked at the and it definitely merges the files together, but doesn't allow for the programmatic rules that I want to define. Seems promising, but the.NET version of it seems underdeveloped, which is unfortunate. Anyone have any suggestions for either scriptable XML Diff/Merge tools and/or.NET libraries (paid or free)? After a couple days of messing around, I found a solution that I think works for me.
Maybe it could work for other people as well. Was a viable option. When you Diff first file against the second file it creates an XML 'DiffGram' listing what changes it detected between the two XML files. To take care of all 3 rules that I listed above, I Diff'd the two files in one direction, then opened the DiffGram file using Linq-to-XML and Removed all the 'Add' and 'Remove' lines.
XNamespace xd = 'var doc = XDocument.Load(diffGramFile); doc.Root.DescendantsAndSelf(xd + 'add').Remove; doc.Root.DescendantsAndSelf(xd + 'remove').Remove; Then I patched up (merged) this edited diffgram against the first file and created a partially merged temporary file. This takes care of Rules 1 and 2. Next, I Diff'd the partially merged file against the first file used. Then opened the new DiffGram and removed all Change references to 'UseExistingValue'. Var newdoc = XDocument.Load(diffGramFile); newdoc.Root.DescendantsAndSelf(xd + 'change').Where(x = x.Value 'UseExistingValue').Remove; And merged this edited DiffGram against the partially merged file which takes care of Rule 3. Saving this out to XML then produces the final XML merged according to the rules defined above.
Hopefully this can help out other people. HINT: After installing the XmlDiffPatch library, the XmlDiffPatch DLL can be found in C: Windows assembly GAC XmlDiffPatch 1.0.8.28b03f5f7f11d50a3a XmlDiffPatch.dll.