As a programmer that loves frameworks like Ruby on Rails, one frustration I always had with .Net was the lack of frameworks that were easy to use and just worked. When I started work at my current employer’s in January, they had a framework that had previously been developed that they were using. I went on using it and making modifications to it so that it would continue to meet our needs and complete simple tasks.
A few weeks ago, I friend of mine showed me LINQ to SQL and after 30 seconds of reading up on it I was hooked. Why hadn’t I seen this before? It has been in the .Net framework for some time as far as I can see. I suppose it was another one of those cases where you don’t notice it until you need it. That is one issue I do have with .Net, it has so many features and yet you may never even know half of the things that it is capable of. That’s a conversation for another day though. LINQ to SQL allows you to easily create objects that you can interact with which also includes features such as:
- Parent/Child entities
- Stored Procedure calling as methods
- Customisation and the ability to override all of the methods and classes
- and much more
To find out more on LINQ to SQL, I recommend reading the following series from Scott Gu’s blog.
Until next time!
Cameron
|
Adam |
You should have a look at the ADO.NET Entity Framework. While LINQ2SQL is still supported, the Entity Framework is Microsoft’s flagship data access framework.
Cameron |
I will have to try it out. So far I have found no major problems with LINQ2SQL and therefore haven’t felt the need to move away from it. Maybe if I try ADO.Net I will be convinced otherwise. Thanks for the recommendation.