Solving LINQ's N-Tier Issues

project scope

project scope — Sat, 10 May 2008 16:40:52 GMT

Pingback from project scope

cool stuff

cool stuff — Sat, 10 May 2008 08:47:01 GMT

Pingback from cool stuff

re: Solving LINQ's N-Tier Issues

Sameer C Thiruthikad — Thu, 08 May 2008 11:19:22 GMT

Why don't you just tell us what's your solution in few words... and then we can decide to download the code and see if it fits our purpose.... Thanks :)

re: Solving LINQ's N-Tier Issues

Freakyuno — Wed, 07 May 2008 22:33:30 GMT

Jeremy,

You're correct of course, there are many ORM tools out there. There are a few that do just basic object mapping, a few that generate connection objects, and a few that do both, the ones that do both = LINQ, and they suffer from the same problems with attached objects.

re: Solving LINQ's N-Tier Issues

Jeremy D. Miller — Wed, 07 May 2008 18:55:06 GMT

If Linq to SQL is that much of a problem, why not simply use a different tool? There's a slew of other ORM tools out there.