I've recently been working with LINQ and in particular, DLINQ. My concern is where to use it in a tiered application. When we developers begin to develop an application, we stick to our concept of tiers which include the presentation layer, a business logic layer and a data access layer. Many of the examples on MSDN show databinding to controls that allowing databinding to anything that inherits from IEnumerable. So in the future to keep an application consistent and easy to maintain where should we be using LINQ?

If in the data access layer we return back arrays of objects or objects of IEnumerable this sounds like the best approach to keeping the presentation layer seperate from the bll and dal. I like the flexibility of LINQ and the ability to still be able to utilize stored procedures and other db objects as we're already used to. As we begin to move out our db queries into .net languages, it will be interesting to see how sql server and tsql play a role in future development.