P
Pablo
Hi, just trying to get to grips with data access in ASP.NET 2.0.
I may be missing a huge point here, and please forgive if I am, but in
ASP 1.x and OO applications best practice suggests abstracting our
various logic into distinct layers - we would have the UI in one layer,
business logic in another, and data access performed by another. We all
know that.
ASP.NET 2.0 seems to be moving us away from this. I'm not doubting that
with SqlDataSources we have an extremely useful component, but with its
easy of use it is surely moving developers away from the above model.
Like I say I've just picked up the book so to speak on ASP.NET 2.0 this
week, but I'd like to invite more experienced developers to tell me if,
and how, I'm barking up the wrong tree or not!
Many thanks in advance and happy coding!
I may be missing a huge point here, and please forgive if I am, but in
ASP 1.x and OO applications best practice suggests abstracting our
various logic into distinct layers - we would have the UI in one layer,
business logic in another, and data access performed by another. We all
know that.
ASP.NET 2.0 seems to be moving us away from this. I'm not doubting that
with SqlDataSources we have an extremely useful component, but with its
easy of use it is surely moving developers away from the above model.
Like I say I've just picked up the book so to speak on ASP.NET 2.0 this
week, but I'd like to invite more experienced developers to tell me if,
and how, I'm barking up the wrong tree or not!
Many thanks in advance and happy coding!