Building a data access layer using LINQ to SQL and the ADO.NET Entity Framework allows you to decouple your application from the persistence technology you're using.
MSDN Magazine December 2008
View Complete Post
Julie Lerman shows database administrators how to limit access to databases from the Entity Framework by allowing it to work only with views and stored procedures instead of tables-without impacting application code or alienating developers.
MSDN Magazine August 2010
Here the author answers questions regarding the Entity Framework and provides an understanding of how and why it was developed.
MSDN Magazine July 2008
The System.Data.dll assembly in the .NET Framework contains namespaces whose base classes can be used to create custom data providers. These namespaces also define a number of data access interfaces and base classes that let developers create data providers that will interoperate with other custom providers. Using the ADO.NET classes Connection, Command, DataReader, and DataAdapter, writing a provider is easier than writing one for OLE DB. This article explains these classes and their implementation, and how they can be used to write a variety of different kinds of data providers.
MSDN Magazine December 2001
I was rummaging the internet learning aspx and came across the concept of: Microsoft Application Block for Data Access in .NET
It seems great of course. The articles are all early 2003-5 such as
So the question is - is this tech still relevant and should I be using it?
Ive just started a project that will use the enterprise library 4.1 data access code blocks. Its been years since ive used them, can anyone tell me what assemblies I need to reference in my project in order to use them ? Ive referenced
are there any others I need ?
The entlib 5 sugest me to use with data accessors for mapping data from database to my data objects (ORM).
But in .NET 3.5 and especially in .NET 4, I can use in entity framework as ORM methodology for data objects.
What data accessors uses advantages over the entity framework?
What differences that should be affect on my using decisions?
Elisa Flasko takes you through a sample weblog application to demonstrate how new improvements in Entity Framework and WCF Data Services work together to simplify the way data is modeled, consumed and produced in Visual Studio 2010.
MSDN Magazine April 2010
Building an NHibernate-based desktop application isn't any harder than building a web application, and in many cases NHibernate simplifies elements of session handling and concurrency.
MSDN Magazine December 2009
Developers deploy a wide variety of development philosophies and architecture styles. This article explores three common perspectives on application development and describes how the Entity Framework can be employed in each. Specifically, the article looks at the forms-centric, model-centric, and code-centric development styles and their relationship to the Entity Framework.
MSDN Magazine August 2009
In this article, the author delves into some commonly used ways of writing data access code and looks at the effect they can have on performance.
In this article the author looks at two versions of the same application--one consuming an on-premise Data Service, and one consuming an Azure Table Data Service to illustrate data access in the cloud.
MSDN Magazine May 2009
Here we build a solution that fits the Entity Framework into an n-tier architecture that uses WCF and WPF and the MVP pattern.
The Entity Framework is a hot topic, but how do you know when to use EntityClient, Object Services, Entity SQL, or LINQ? Find out here.
MSDN Magazine May 2008
The new Entity Framework in ADO.NET will let you manipulate data using an object model. John Papa explains.
MSDN Magazine July 2007