Over the part few months, I'm using LINQ to SQL in my .Net projects.. It's one of the most attactive features I've in .NET Framework 3.5 .. Al tough the full release of LINQ to SQL is scheduled with upcoming Visual Studio Orcas; but still Visual Studio 2008 has most of its features..
Those who dont know anything about LINQ; well LINQ stands for Language Integrated Query and as the names shows LINQ is Code based language designed for data manipulation in different data structures like Lists, Array, KeyValue Pairs etc..
What is LINQ to SQL?
LINQ to SQL is an 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.
(Taken from ScottGu's Blog)
Reasons I Choose Linq to SQL
Reason number one.. LINQ is Cool :) Actually there are so many reasons for going with LINQ to SQL..
Let's Get Started
Im breaking it in following parts..
Those who dont know anything about LINQ; well LINQ stands for Language Integrated Query and as the names shows LINQ is Code based language designed for data manipulation in different data structures like Lists, Array, KeyValue Pairs etc..
What is LINQ to SQL?
LINQ to SQL is an 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.
(Taken from ScottGu's Blog)
Reasons I Choose Linq to SQL
Reason number one.. LINQ is Cool :) Actually there are so many reasons for going with LINQ to SQL..
- LINQ is quite easy to understand
- Ddata manipulation can be done without breaking your nerves
- SQL Injection threat is very low.. Almost negligible
- We can use one single language through out the project both for Database Quering and internal data structures
- and bla bla bla...
Let's Get Started
Im breaking it in following parts..
- Creating the project
- The LINQ to SQL Connector and Data Context
- Whats the difference in LINQ And SQL Queries?
- Simple Queries
- Some Data Manipulation