And we're back to pros and cons.

I have a medium priority project where I'm building a LINQ provider around the API of a third-party product that we're heavily integrating into the corporation. I'm learning a lot about how LINQ works. This isn't stuff you would learn just by using LINQ.

>But then look at the things you learn along the way. Isn't that part of the gardening? :)
>
>From my own perspective, I learned a good bit about the inner workings of ADO.NET, Generics, and stored procs by spinning my own DAL. There are many stories out there like that. Sure, out of the box EF provides value But value comes from many sources, and that's basically my point.
>
>Here's another example - Change Data Capture in SQL 2008 reduces (doesn't eliminate) the need for triggers. And as much as I wish they'd implemented CDC earlier, many developers who got their hands dirty for years with triggers wound up learning other things along the way.