Home » c# » DataSets, ObjectDataSource and 3-Tier ASP.NET

DataSets, ObjectDataSource and 3-Tier ASP.NET

As I’ve mentioned in other post, while I think LINQ has it’s uses, I still favor the use of the ObjectDataSource control in conjunction with DataSets and a 3-tiered architecture.  Since any future demos I do will probably involve this architecture, I thought it would be useful to do a short demo that demonstrates how to create a 3-Tiered architecture in ASP.NET.

 

Other post in c#

About Dave Bush

Dave Bush is a Full Stack ASP.NET developer focusing on ASP.NET, C#, Node.js, JavaScript, HTML, CSS, BootStrap, and Angular.JS. Does your team need additional help in any of the above? Contact Dave today.

Leave a Reply

3 Comments on "DataSets, ObjectDataSource and 3-Tier ASP.NET"

Notify of
avatar
Sort by:   newest | oldest | most voted
trackback

[…] Datasets ObjectDataSource and 3-Tier ASP.NET Datasets StoredProcedures and 3-Tier ASP.NET Swapping Out the Data Access Layer Swapping the Data Access Layer Abstractly Using Reflection to Load a Class in ASP.NET […]

Joel
Guest
I started out using SqlDataSource controls in ASP.NET, then moved to custom classes to have the separation between presentation, logic, and data access, but the overhead of doing manual CRUD for every custom class was prohibitive. I’m relatively new to both typed datasets and Linq2Sql (and Linq in general), so if I’m misunderstanding something, please correct me. But I’m not entirely sure I understand why you prefer typed datasets over Linq2Sql classes. From my understanding (and I’m asking this to clarify this issue in my own head), unless I’m misinformed, Linq2Sql should be more efficient, in terms of both productivity… Read more »
Dave Bush
Admin
Wow Joel. You’ve posted 3 times in one night?! OK.. let me see if I can address some of your items. First thing. When you use a typed dataset, you would NEVER retrieve all of the data and THEN filter it. You’d create a stored procedure that returned what you wanted and then create an appropriate method in your BLL that would then return that data. So, the only real benefit, as you’ve already stated is that you don’t have to write the stored proc. But, since LINQ is essentially SQL using VB.NET or CSharp (or whatever other language) syntax.… Read more »
wpDiscuz