LINQ Farm: LINQ to XML and Line Numbers

DotNetKicks.com — Sat, 27 Sep 2008 00:41:47 GMT

You've been kicked (a good thing) - Trackback from DotNetKicks.com

re: LINQ Farm: LINQ to XML and Line Numbers

ravenex — Sat, 27 Sep 2008 05:10:42 GMT

Hi,

Thanks for the article. I'd like to ask though, can a XDocument be saved back to a file in the exact line numbers as it was loaded? There doesn't seem to be such an option in SaveOptions

LINQ Farm: Preserving Formats with LINQ to XML

Charlie Calvert's Community Blog — Tue, 30 Sep 2008 21:08:05 GMT

In a previous post , you saw how to work with line numbers when using LINQ to XML to read a file. This

re: LINQ Farm: LINQ to XML and Line Numbers

Charlie Calvert — Wed, 01 Oct 2008 00:00:40 GMT

Ravenex,

Thanks for your question. It is interesting. Does the Preserving Formats post linked too above help, or were you after something else?

- Charlie

re: LINQ Farm: LINQ to XML and Line Numbers

ravenex — Wed, 01 Oct 2008 06:02:36 GMT

Charlie,

The new post does give some insight into how it might be done. My goal was to be able to do least amount of modifications to an XML source file when editing with an editor I wrote. The editor shows the tree hierarchy of XML document, and users can't see the actual text in the source file, so line numbers didn't really matter. It would have just worked, but when the files are checked into repository, reformatting the source files will cause versioning control report more modifications then there need to be. That's why I wanted to do the least amount of modifications when editing, and perserving line numbersis crucial.

Thanks,

- Ravenex

re: LINQ Farm: LINQ to XML and Line Numbers

SkipSailors — Thu, 16 Oct 2008 07:52:11 GMT

I have:

document.Validate(schemas, (o, e) =>

{

Console.WriteLine("{0} at {1}",

e.Message, e.Exception.LineNumber);

error = true;

true);

reporting errors always at line 0. I use the LoadOptions.SetLineInfo. Does this have anything to do with what you are talking about here?

re: LINQ Farm: LINQ to XML and Line Numbers

OpticTygre — Sat, 25 Oct 2008 17:30:08 GMT

Hi Charlie,

I'm actually working with line numbering in VB, attempting to perform more advanced things.

The IXmlLineInfo interface provides a good option for discovering the line number and line position for the start of an element, node, or text. Is there a way, however to get the ending line number of an element and text?

Through my endeavors of answering that question, I have discovered some interesting things in Linq to XML. If you're interested, please read my forum comments at http://social.msdn.microsoft.com/Forums/en-US/vbgeneral/thread/a485f9b7-58a3-4da3-8654-6c1b53e7f5ba.

Thanks for any advice you can provide!

re: LINQ Farm: LINQ to XML and Line Numbers

OpticTygre — Sat, 25 Oct 2008 19:46:31 GMT

To further explain my comment above, I believe a brief example should be provided. Take the following XML:

<A>

<B>

<D>

<![CDATA[

This is some other data

that may take several lines

]]>

</D>

</B>

</A>

In this XML, all we know from IXmlLineInfo is the starting line number of each element, and the starting position of each element. We don't know:

1) The ending line number of each element.

2) The ending line number of text or CData

3) The ending line position of each element (though this should be the same as the start position)

4) The ending line position of text or CData.

I believe the heart of the problem lies in the fact that even though the NodeType property of an XNode is of type XMLNodeType, the XNode object does not use all of the node types available. Looping through this XNodes of this XML, and printing out the NodeTypes, you will notice that and XNode treats <A> and </A> both as Elements, and not an Element and EndElement.

-Jason