We just bought a number of licenses. I am quickly getting up to speed in order to create training videos on how to use **LLBL **and do a presentation to the rest of the developers.

One of the questions will be about how **LINQ **will remove/replace parts of the system. Notably filters and predicates.

Will post-**LINQ **launch allow us to use LINQ to do the same as filtering/predicates does now and will **LINQ + lamba **expressions then be the replacement for these and other LLBL objects now used?

A road map for how LLBL will interact with LINQ would be fantastic.

Ian

ianvink wrote:

We just bought a number of licenses. I am quickly getting up to speed in order to create training videos on how to use **LLBL **and do a presentation to the rest of the developers.

One of the questions will be about how **LINQ **will remove/replace parts of the system. Notably filters and predicates.

Once Linq's syntaxis has been more stabilized (MS is changing it still), we'll release a Linq support assembly which works with your generated code and the runtime lib and will effectively convert Linq's Expression tree's to LLBLGen pro predicate/relation etc. objects and more. We think a bit of code generation is required as well, but that's not a big deal .

I think it will be summer 2007 when this will be released.

Linq will be a 'supported' query formulation system for LLBLGen Pro, we will also keep our own objects, as LLBLGen Pro supports more features than you can express in Linq.

Will post-**LINQ **launch allow us to use LINQ to do the same as filtering/predicates does now and will **LINQ + lamba **expressions then be the replacement for these and other LLBL objects now used?

You will be able to use Linq instead of predicates, relation collections and the like, though at some point you will need to call extension methods though that's not that much of a problem (as the C# syntactic sugar which below the surface calls extension methods, doesn't support all constructs possible as far as I can see it now)

A road map for how LLBL will interact with LINQ would be fantastic. Ian

The plan is to have you write Linq code without knowing you're querying llblgen pro code, i.o.w.: full Linq support. As we also keep on supporting our own objects, you have an easy migration path.