I understand how XPath works. I was trying to hint that we don't really need to use XPath when there are plenty of other methods available in XmlNode and friends that do everything we're using XPath for.
My gripe against VS.NET is that it's forcing us to use namespaces in order to get the IntelliSense feature. To me, that's a deficiency in VS.NET. Jason ----- Original Message ----- From: "Scott Hernandez" <[EMAIL PROTECTED]> To: "'Jason Diamond'" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> Sent: Wednesday, April 17, 2002 3:10 PM Subject: RE: [nant-dev] nant.xsd sample > The context issue is actually defined in the XPath W3C Standard[1]; and > is supposed to work that way. As for validation, we can do it without > the namespace, but if want intellisense and leave the namespace in, all > of the xpath queries will fail unless we code it. > > [1] > http://groups.google.com/groups?hl=en&selm=Ojp6QPIUAHA.279%40cppssbbsa03 > > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]] On Behalf Of Jason > Diamond > Sent: Wednesday, April 17, 2002 2:40 PM > To: [EMAIL PROTECTED] > Subject: Re: [nant-dev] nant.xsd sample > > [snip] > > It's unfortunate that VS.NET requires a targetNamespace in XSDs in order > to > use IntelliSense especially since XSDs are perfectly capable of > describing > documents that make no use of namespaces. I ran into this (and probably > the > other problems you mentioned) just yesterday for a different project. > It's > frustrating because VS.NET is _sooo_ close to being perfect but not > close > enough to where you can actually use it. > > Jason > > > _______________________________________________ Nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
