So my teammates have been complaining about how "hard" using LLBLGen was. (Ive been using it since 2004 so its no biggie for me, its the only way to fly IMO).

So I asked them "If we could use the declarative Linq syntax to fetch data from the db and stop writing classic style ORM style / OO Style code, would it be easier for you guys."

They all said "Yes, we like declarative languages, so yeah, linq is cool..."

So, I copied my 2 generated code libraries, my hand coded data access project, and my hand coded unit/integration tests projects into a new location.

Opened the 2.5 .lgp file, using the 2.6 designer, refreshed the schema, clicked generate, selected .NET 3.5, selected the linq templates, then sql specific templates, then selected the Adapter.TwoClass2008 option, and clicked run.

All the code was generated.

All the code compiled.

All of the 125 integration/unit tests passed, and they ran ALOT faster (dont quote me but I think we went from 30s to 6s, I can find out if you really want to know).

So, in about 15 minutes I was able to upgrade from 2.5 to 2.6 and now we have a faster faster data access codebase, with Linq support.

So the moral of the story is that -> You guys rock. -> You save me a ton of time -> Keep up the great work.

Cool!

Thanks for the kind words. Yes Linq was a true PAIN to implement but it really pays of. v2.6 is indeed faster than v2.5, I don't think there's much room for improvement left in the framework, unless profilers get better and reveal hidden bottlenecks .