EDIT
Appreciate all the inputs guys. The opinions were very welcome, I think that we will go with the implementation of L2S at this stage and just minimize or encapsulate our DAL in such a way that if we need to switch to EF in the future, it will not be a very painless operation.
As it was quite subjective, the glasses hit the poster with the most revolutions.
ORIG
I tried to keep up with the whole Entity Framework Vs. Linq2SQL theme and there is already some Q on SO, for example.
Entity Framework Vs. Linq To Sql
What is interesting to me (an opinion is welcome), if you are starting a new large project, you would use Linq2SQL for your level of data access.
To give some context, we are .NET C # House, DB is SQL Server 2000, but we may be porting this to SQL 2005 later this year. And of our small development team, I am the only one who has experience with C # 3.0 / .NET 3.5. All other team members have been stuck in 1.1 / 2.0 over the past 3 years, using manual cut ADO.NET and the SqlHelper code for the data access layer.
I suppose my main concern is that we will start this new project with something more advanced / useful / accelerated for development with (i.e. L2S), but in the end it is already deprecated.
If we take a hit, delay the project and explore it using the Entity Framework in VS2008.
Cheers for any input guys.