Devart Forums

Please help me decide. I cannot choose between the two technologies:
Entity Framework:
pros: Integrated into Visual studio design tools, the library references are added automatically.
cons: Cannot handle IN clause.

LINQ to SQL:
pros: can handle the IN clause
cons: library references should be added manually,
once the classes are generated and you decide to add more tables to generated context classes you have to start from sratch by again choosing all tables (and I am choosing from hundreds of them).

Am I doing something wrong?
BTW, which one supports Oracle's hints? I have to use them sometimes.
Thanks

We recommend using our Entity Developer tool which is included with dotConnect for Oracle installation. Now it is a separate tool which is launched when you open Devart LINQ to SQL or Entity Model in your project. We plan to integrate it fully in Visual Studio in the future versions.
Hints to the mentioned pros&cons:
1. The necessary references are added automatically when you add Devart LINQ to SQL Model or Devart Entity Model.
2. Here is the discussion about IN clause in Entity Framework:
http://social.msdn.microsoft.com/Forums ... e4a1ab59f0
3. Adding new classes. You can open your previously generated model in Entity Developer, drag&drop new tables from Database Explorer to designer surface, click the Save Project button - the new classes will be added to your model.
4. Oracle's hints are not supported via LINQ to SQL or Entity Framework, but you can execute SQL Queries with Oracle's hints directly (for example: http://msdn.microsoft.com/en-us/library/bb399403.aspx ).