Home/ Questions/Q 167909
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-11T12:21:33+00:00

I was just reading about Linq to SQL being discontinued. For a while I

  • 0

I was just reading about Linq to SQL being discontinued. For a while I put off learning Linq at all. Even on asp.net, when I last checked, their data access tutorials were using table adapters and bll classes. Then there are linq tutorials. Now that I have read this and that the Entity Framework is the new way to go, does that mean all the Linq ‘stuff’ I have been reading about for a year and a half, how great it is, etc., is all this just gone? No one ever seems to settle on the right way to do things or at least some standard way with MS products. And I understand that you can’t say one way is right for everything. But, in this particular case I do not understand why there cannot be some settling on data access.

Or, is Linq To SQL just the ORM portion of Linq? What exactly would I learn now if I wanted to use an ORM? I have read several things on StackOverflow, but none that really help me know what to do.

It seems that nHibernate may be better than any of the Microsoft choices. Yes, I know there are others (subsonic, and others were mentioned in various SO questions.)

Thank you.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. No.

    LINQ to SQL is built on top of LINQ, which is one of the fundamental added language features in .NET 3.5 Framework.

    Technically other ORMs can implement their own LINQ systems, e.g., NHibernate already has LINQ to NHibernate going. This is on top of the ones provided in the framework, such as LINQ to XML, LINQ to Objects etc.

    • 0