The .NET LINQ to XML Explorer tool makes it easy to browse an XML document tree created by Microsoft LINQ to XML.
With the .NET LINQ to XML Explorer tool you can now examine the result of how LINQ to XML converts an XML document into an object tree and serializes that object tree into a text string without stepping through XElement, XNode and XAttribute object tree navigation methods during Visual Studio debugging sessions.
Just enter arbitrary XML content into the .NET LINQ to XML Explorer tool's text editor, or even compose an XDocument document tree in C# code, and examine what is being created by .NET LINQ to XML.
.NET LINQ to XML Explorer provides many features for examining how LINQ to XML decodes and encodes XML:
Enter XML or C# code easily using the full-fledged text editor:
- Copy/cut/paste text
- Drag & drop text and text files
- Find/replace text (you can even use regular expression search terms)
- Load and save your XML source document or C# code for later retrieval
NB: The .NET LINQ to XML Explorer text editor does not provide code editing features like code completion, automatic indentation or syntax highlighting.
Explore LINQ to XML using these great features:
- Choose between two modes for entering XML data:
- Plain XML text
XDocumentconstructor, written in C#
- Get the resulting LINQ to XML object tree visually displayed
- Examine XML output created from the
XDocumentobject tree - Optionally display white-space characters and non-printable ASCII characters
.NET LINQ to XML Explorer can be used in two different modes:
Either enter literal XML text:
or create an XDocument tree
Use the View > Use LINQ to XML menu item to switch between Literal XML and LINQ to XML mode.
Literal XML text is evaluated immediately while you are typing. LINQ to XML content, however, will be evaluated when the Submit button is clicked.
Hover over an individual icon in the tree to unveil more of that XML node's details, e.g., the node's namespace.
Errors encountered while evaluating the XML or LINQ to XML text will be displayed in the lower right panel:
You can examine the XML document that is created from serializing the underlying XDocument by selecting View > Show XDocument XML Output or the corresponding toolbar button 
:
The XML output panel comes with three different formatting options:
Disable Formatting
- Preserves all insignificant white space while serializing.
Omit Duplicate Namespaces- Removes the duplicate namespace declarations while serializing.
Show Control Characters- Escapes all non-printable ASCII characters
Reach any of these options by selecting menu items available in View > XDocument Formatting Options or use the corresponding toolbar buttons right above the XDocument output panel.
The Microsoft WPF TextBox displays the tab character using a fixed width of eight spaces which is undesirable most of the time. So, by default, .NET LINQ to XML Explorer converts tab characters into space characters. This automatic conversion can be disabled in preference settings using the Tools > Options menu item.
When converting tabs into spaces, .NET LINQ to XML Explorer intelligently inserts as many spaces as a corresponding tab character would have displayed.
When you open a file, .NET LINQ to XML Explorer automatically performs an initial spacing conversion if enabled. The file will not be considered "modified" though. So, only the changes you make to the text will be considered a "change".
Use .NET LINQ to XML Explorer's options setting found at Tools > Options for disabling the tab character to space characters conversion as well as changing the number of spaces represented by the tab character.
In LINQ to XML mode, when you enter LINQ to XML into the text input box, make sure the final statement is an expression. Expressions in C# do not end with a semicolon.
So while this will work:
XDocument xd = new XDocument()
xdThe following version doesn't:
XDocument xd = new XDocument()
xd;As you may see, there is a (redundant) trailing semicolon in the second version.
.NET LINQ to XML Explorer will try to remove trailing semicolons from your LINQ to XML code when evaluating your code, but fails doing so when semicolons are not the final non-whitespace character. This is, for example, the case when your final statement is followed by a comment.