I've been reading and watching alot on LINQ recently, and I really like the look if it. The problem is I just dont see where it would fit into any of my applications. The current architecture I use is:
Website project containing UI
Assembly containing BLL
Assembly containing DAL providers (CRUD operations)
Assembly containing DTO to pass around between layers
I dont use (or wish to start using) any kind of embedded SQL in my application. All queries are written by using sprocs or UDF's. All select operations are written using a data reader and then the provider class in my DAL maps the columns to my DTO objects.
The main problem with this approach is the amount of code that is really mundane and duplicated, for example mapping a resultset to custom entities and adding parameters to stored procedures to execute...
I can see that LINQ may help with the problem. But is there any need to add another tier almost? In an ...
Go to the complete details ...