Who is actually using LINQ or LINQ to SQL?

Microsoft UK sends out these MSDN Flash newsletters once in a while. Every one of them has this poll with some .NET related question and the results come in the next letter. I got the latest today and last time the poll was about the following:

What really amazes me is the high number of LINQ to SQL and especially LINQ to Entities projects starting on January 1 2009. From what we hear at Class-A from every contact we’ve got, very, very few people are using LINQ, let alone LINQ to SQL. Entity Framework isn’t even something people think about using for production code.

So my question to you is

  • are you using LINQ, LINQ to SQL or any other flavor in production code and what are your experiences?
  • Are you using .NET Framework 3.5 anyway? Are you still on .NET Framework 2.0?

You may also like...

13 Responses

  1. Erwyn van der Meer says:

    Yes, we used .NET 3.5, LINQ and LINQ to SQL on my previous project. I highly prefer LINQ to SQL over just plain ADO.NET. You can even still use stored procedures with LINQ to SQL if you really want to…

  2. Michiel Borkent says:

    I’ve used LINQ2XML and LINQ2SQL myself in my previous jobs and projects. .NET 3.5 because of the lambda expressions, anonymous types and automatic properties. It’s just a little more comfort, not something I couldn’t do without. Hope to learn some more cool LINQ stuff at the Data Access course at Class-A. Won it at CodeCamp 2008 :).

    PS, I’m available for a job right now in the neighbourhood of Amersfoort. Anyone reading this, if interested I could send you my CV. Just send a msg to [email protected].

  3. Dennis van der Stelt says:

    @Michiel : Congrats! You’ll definitely learn more LINQ at the Data Access course!

    And rofl at the job you’re available for! 🙂 Good luck with it!

  4. We are using 3.5 (ok), and LINQ to SQL (nice), and straight LINQ (amazing) for a new project.

  5. Robb says:

    I have been used LINQ to SQL, LINQ to XML and LINQ to Objects on large production enterprise sites for the last 9 months.

  6. Ramon Smits says:

    NHibernate in 80% of all stuff I do with databases. I haven’t found any really good reason to use linq2sql or any other ms framework at the moment.

    And yes of course I’m using 3.5! Sometimes I open ‘legacy’ projects and start using 3.x features and wonder why it can’t compile 😛

    I’m using linq *very* frequently but thats more because it makes it sooo easy to process hiearchical in memory data.

  7. Jens says:

    We’re using .NET 3.5 and Linq To SQL for a new project we’re currently working on.

  8. Kris says:

    Our apps are converted to 3.5, but we’re not using any of the new features yet.

  9. Martin S. says:

    We’re using LINQ2SQ, it’s really great to have this power directly in the language. Beats the alternatives.

  10. pb says:

    Using LINQ for objects all the time, awesome. Sorting, grouping, etc. without it is a pain.

  11. Jorge Diaz Tambley says:

    Subsonic: I am a recent convert and quite satisfied

    regards

  12. Dennis van der Stelt says:

    But how about eager / lazy loading in Linq to SQL? Does no one feel the pain I feel there? Or other issues?

    And from the above results, 100% of the developers use LINQ and most LINQ to SQL. How come I don’t see this reflect in the real world? Anyone has any reason not to use LINQ and .NET 3.5?

  13. Kiri kamal says:

    We are using Nettiers for last 2 years. Now moving to SubSonic…

Click on a tab to select how you'd like to leave your comment

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.