Integrate Linq-to-Sql or Entity Framework in new .net 3.5 applications?
Over the last few months I've been concentrating on the new Entity Framework versions, but from now on I've to build a complete new .net 3.5 application.

I found out it's impossible to use the new EF 4.1 in a .net 3.5 application. But seeing the criticism on the first EF version and the out-of-development status of Linq-to-Sql, what is the best way to go on this date?

What arguments should be used in a choice? Thanks in advance!!
Integrate Linq-to-Sql or Entity Framework in new .net 3.5 applications?
===

Over the last few months I've been concentrating on the new Entity Framework versions, but from now on I've to build a complete new .net 3.5 application.

I found out it's impossible to use the new EF 4.1 in a .net 3.5 application. But seeing the criticism on the first EF version and the out-of-development status of Linq-to-Sql, what is the best way to go on this date?

What arguments should be used in a choice? Thanks in advance!!