Gerry Shaw wrote:
It does seem like a pretty good solution but what we have does work and
has been tested and isn't causing any problems that I know of. Its also
a lot fewer files.
Still it's a pretty good sample and I'll likely use it in other
projects.
Thanks
A sample just (a few
We need to do something. This code fails because there is no file
associated with the document.
XmlDocument doc = new XmlDocument();
XmlElement project = doc.CreateElement(project);
XmlElement echo = doc.CreateElement(echo);
Scott Hernandez wrote:
We need to do something. This code fails because there is no file
associated with the document.
XmlDocument doc = new XmlDocument();
XmlElement project = doc.CreateElement(project);
XmlElement echo = doc.CreateElement(echo);
Scott wrote
My docs don't list XPathNavigator as implementing the IXmlLineInfo
interface. The object browser doesn't seem to show it either. Nor does
the IXmlLineInfo overview list any classes other than XmlTextReader,
XmlValidatingReader as implementers[1].
[1]
My concern about the lines numbers was less about their need (or
accuracy), and more about the fact that the LocationMap generated errors
when the document is not file-backed. If we go with the DOM Extensions
then we can check for the IXmlLineInfo interface before we output the
info.
For now,
Scott Hernandez wrote:
My concern about the lines numbers was less about their need (or
accuracy), and more about the fact that the LocationMap generated errors
when the document is not file-backed. If we go with the DOM Extensions
then we can check for the IXmlLineInfo interface before we
The VS.Net/OtherIDE add-ins :)
But I finish that up after the release.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:nant-developers-
[EMAIL PROTECTED]] On Behalf Of Ian MacLean
Sent: Tuesday, June 04, 2002 3:34 PM
To: Scott Hernandez
Cc: 'NantDev'
Subject: Re: [nant-dev]