Jump to content

Recommended Posts

Posted

I have to say that before I got my hands on VS 2008 and really sat down to write serious code, I wasn't that excited about LINQ. I thought the DB access would be great for small or one-off apps and the XML stuff was nothing new. Some of the LINQ to objects stuff looked alright but I*still wasn't that impressed.

 

Now that I've spent some time with it, I love it. The amount of operations that we do that can be expressed as set operations (projection via Select(), filtering via Where(), grouping, etc.) is nuts. I can rewrite entire methods as one-liners that just use query clauses properly. I'm writing a World of Warcraft combat log parser at home and so far it's basically 2 lines: create a RegEx, run a query that parses the file into an object graph.

 

Extension methods are quite nice as well. I can write Converter classes that move between our internal representations, for example Entry, to an external proxy object, Post, for returning from Web Services. The beauty is that Entry and Post have no idea about each other but I can still write thisEntry.ToPost(). I get awesome separation of objects and great syntax.

 

Anyone else out there having a good (or bad) time with LINQ?

 

More...

 

View All Our Microsoft Related Feeds

  • Replies 0
  • Created
  • Last Reply

Top Posters In This Topic

Popular Days

Top Posters In This Topic

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


×
×
  • Create New...