I would recommend using Entity Framework over Linq to SQL But in both these cases, you have the power of Linq for such queries. Plus this gives you better designer support (intellisense, strong types, compile time checking) EF or LinqToSQL becomes the lower level DAL and on top of this you would use the Repository pattern to call your Data Objects in a loosely coupled way. You could also add special methods for certain repositories to query data in a specific way if this needs to be encapsulated You should search SO for the repository pattern with Entity Framework or LinqToSql, you'll find a couple of implementations See this answer : Advantage of creating a generic repository vs. specific repository for each object?
I would recommend using Entity Framework over Linq to SQL. But in both these cases, you have the power of Linq for such queries. Plus this gives you better designer support (intellisense, strong types, compile time checking) EF or LinqToSQL becomes the lower level DAL and on top of this you would use the Repository pattern to call your Data Objects in a loosely coupled way.
You could also add special methods for certain repositories to query data in a specific way if this needs to be encapsulated. You should search SO for the repository pattern with Entity Framework or LinqToSql, you'll find a couple of implementations. See this answer : Advantage of creating a generic repository vs. specific repository for each object?
I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.