Hello shapper,

LinqDataSource is good, only if you are playing with your project and try
to save some times, but LDS approach is not very good for the serious application
where you are usually using n-tiers systems.

I usually use LDS for the small project where Im not really concern about
design and the result is priority. For other cases ODS is preferable

Btw, there is an overview of LinqDataSource vs ObjectDataSource http://weblogs.asp.net/despos/archive/2007/09/24/linqdatasource-vs-objectdatasou
rce-vs-sqldatasource.aspx

---
WBR,
Michael  Nemtsev [.NET/C# MVP] :: blog: http://spaces.live.com/laflour 

"The greatest danger for most of us is not that our aim is too high and we
miss it, but that it is too low and we reach it" (c) Michelangelo

s> Hello,
s>
s> I have been trying the ObjectDataSource and LinqDataSource with Linq,
s> a DataPager and a ListView.
s>
s> LinqDataSource has some restrictions but it is easier to use than
s> ObjectDataSource which on the other hand is less restrictive.
s>
s> Should I even use a DataSource?
s>
s> Is there any problem of defining all data connections in ListView
s> events?
s>
s> I am almost taking the decision of using ObjectDataSource but
s> sometimes I wonder if I should not use these objects in my project.
s>
s> Thanks,
s>
s> Miguel
s>