Linq, XML and the continuing need for XPath
-
A while back I can't remember who, and I think it was in the lounge, someone mentioned that there was a specific limitation of Linq that can only be solved with XPath. Can anyone remember who said this, or better yet know what the limitation is?
-
A while back I can't remember who, and I think it was in the lounge, someone mentioned that there was a specific limitation of Linq that can only be solved with XPath. Can anyone remember who said this, or better yet know what the limitation is?
-
That's the one. Excellent.
-
A while back I can't remember who, and I think it was in the lounge, someone mentioned that there was a specific limitation of Linq that can only be solved with XPath. Can anyone remember who said this, or better yet know what the limitation is?
martin_hughes wrote:
A while back I can't remember who, and I think it was in the lounge, someone mentioned that there was a specific limitation of Linq that can only be solved with XPath. Can anyone remember who said this, or better yet know what the limitation is?
Sorry it took so long to find this, but you posted the message the day before Developer Day Scotland and I wasn't very active around that point as I was too busy arranging a conference. Anyway... Reasons why you still need XPath (that I've found so far): * Not everything you do can be done purely in .NET * XSLT * Having WiX create an installer that configures the config file
Recent blog posts: * Introduction to LINQ to XML (Part 1) - (Part 2) - (part 3) My website | Blog