Hello Tim,

I would like to know how you would integrate LINQ into your DDD framework. Did you already think about a LINQ variant? Would you use LINQ to implement an alternative repository?

My idea is to save some work on avoiding to implement each single database field mappings and their related tables when using LINQ and reflection, I am not sure if this makes sense.

I would appreciate if you or/and some other readers would share some thoughts.

Best regards,
Hannes

Hannes,

I did in fact spend a lot of time deliberating how to use LINQ in my repository framework, and I came to the conclusion that you could use it if you wanted to behind the walls of the repository interface. Basically, it is not part of the framework, but any repository can use whatever it wants to get at the data it needs. I thought about making a generic repository that would take in LINQ lambda expressions for doing selections, but I did not feel that it was worth the effort.

I wanted to use the ADO.NET Entity Framework, but I really hated using it. LINQ to SQL was even worse. So, I just kind of threw in the towel and went with what I had, in hopes of changing it to use the EF once it got a lot better.

Thanks,

Tim