Hello, Thanks for helping :)
I haven't looked at ADO Entity Framework but I'll check it out. ADO is a bit deprecated nowadays, isn't it ? I mean with LINQ-to-SQL getting more important. The problem I've experienced with LINQ-to-SQL is that even though you don't have to map it to a database schema, it always generate this awful amount of code for all the class you create. It just assumes you want to persist every single class objects to the database, which is not always the case. What I want really is just generating the DataContract classes for my WCF service, but the DataAccess layer should be separated. Using LINQ- to-SQL seems create a strong relationship between my classes and the database's tables, which I don't like.
