Linq To Sql POCO Support

Persistence Ignorance in LINQ to SQL

Jomo Fisher -- C#, LINQ and Whatnot — Tue, 28 Aug 2007 21:45:28 GMT

Mathew Charles is a member of the LINQ to SQL development team. He's posted a great article on POCO support

Persistence Ignorance in LINQ to SQL

Noticias externas — Tue, 28 Aug 2007 22:37:19 GMT

Mathew Charles is a member of the LINQ to SQL development team. He's posted a great article on POCO

re: Linq To Sql POCO Support

johnrusk — Sat, 29 Dec 2007 12:03:18 GMT

I've been investigating using LINQ to SQL with a POCO approach. Based on work so far, I’m satisfied that lazy loading actually _is_ possible with POCO...

Architecting LINQ To SQL Applications, part 5

Ian Cooper [MVP] — Sun, 17 Feb 2008 20:50:46 GMT

Let's return to the series on how to architect applications that use LINQ To SQL. First of all, for

re: Linq To Sql POCO Support

benja — Tue, 19 Feb 2008 04:26:16 GMT

Hi!,

I'm writing some post about using Linq in a N-Tier scenario, including Linq To Sql POCO Support,

I referenced your article here:

http://blog.pampanotes.com/2008/02/first-thoughts-on-designing-linq.html

Thanks a lot,

Benjamin Eidelman

POCO with LINQ to SQL, Insert failed when Reference entity is null?

LINQ in Action roller — Fri, 04 Jul 2008 13:09:45 GMT

Hi, there I'm trying to implement LINQ to SQL with POCO way, and I found a post from Mathew Charles,

re: Linq To Sql POCO Support

Oppositional — Thu, 25 Jun 2009 22:15:15 GMT

Mathew,

I typically do not expose a setter for collection based properties, as the collection is manipulated through its.Add() and Remove() methods.

If I have a POCO class that exposes a collection as a property without a setter, how do you suggest implementing the mapping such that the collection's items are materialized?