Monday November 30th

Friday November 27th

Using LINQ to SQL (Part 1)

"LINQ to SQL is an O/RM (object relational mapping) implementation that ships in the .NET Framework "Orcas" release, and which allows you to model a relational database using .NET classes. You can then query the database using LINQ, as well as update/insert/delete data from it. LINQ to SQL fully supports transactions, views, and stored procedures. It also provides an easy way to integrate data validation and business logic rules into your data model."


This post starts a series about LINQ that is IMO the most comprehensive coverage of the topic. The more you read the more you grasp the power of LINQ (and the VS support).
IMO Linq will be the prevalent means of data access tomorrow, replacing ADO.NET datasets (which really _is_ a change in strategy) and homegrown ORMs.

OK I am new for LINQ I am not familiar with technology, and I want to ask Why I should start use LINQ, why LINQ is better than ohter ways to connect to database.Easier sintacsys is not good enough for me , is there something that LINQ gives you that no other method to connect to database doesn't.we made a reaserch in my company is it worthy to convert all project to LINQ this labour-consumption task , o help me to make a right decission.

LINQ isn't only about connecting to a database or just one ORM among others. Just learning to use LINQ to Objects effectively is very powerful. I think that learning LINQ is important if one wants to be efficient with C# or VB.NET. I'm sure that the importance of the LINQ will grow in coming versions of .NET.

Btw, one example how powerful LINQ is: Raytracer built with a single LINQ-query: (Not very efficient, but shows the expressiveness)

Commenting on Stories is limited for now and will open up to those recommended by the community. Learn how
Loading DotNetKicks...
brought to you by the Kicks Network