I Am in Love with LINQ

I have been reviewing LINQ since last year, but I had never had a chance to actually jump and use it extensively. My last project uses Visual Studio 2008, and there are opportunities to use LINQ.

Probably because I have reviewed it before, the learning curve was not that steep. I use LINQ to SQL and LINQ to XML, and I love it. Prior to use LINQ, I had to open my XPath reference book when I was dealing with XML and XSLT. Now, I don't really have to deal with the plumbing, and let LINQ does it for me. It increases my productivity. Troubleshooting is much more straightforward.

LINQ to XML does not replace the flexibility of XPATH and XSLT. I still like the level of control and flexibility that XSLT and XPATH provides, but for most of the time, LINQ to XML serves my need.

So, if you are using Visual Studio 2008, I encourage you to check it out.

Comments (3)
  1. Wesner Moise says:

    But you can do everything that XPath and XSLT does with LINQ to XML. What’s missing?

  2. Hi Wesner,

    I wrote an application that convert one Xml to another Xml, and to Html using Xslt, and the Xslt can be edited and assigned dynamically, during runtime.

    LINQ can do that, but I have yet to see how LINQ can do that dynamically by simply editing a text file. But most of the time, I deal with Xml that has a static schema, so LINQ is enough.

Comments are closed.

Skip to main content