Last Friday I showed how to use DataSet, the ObjectDataSource and select statements. Today, I’ll start with the project we ended up with last week and convert it to use stored procedures instead and I won’t write any code. That is, only the DataSet is going to change. The rest of my code will stay exactly the same as it was when we started.
Like this Article? Subscribe to get every article sent to your email.
- Swapping Out the DAL One of the comments that showed up on the blog post about using 3-tiered with DataSets and the ObjectDataSource was, "How do we set this up so that we can swap out the DAL?" The […]
- 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. […]
- Using DataSets to Process XML I started a project recently that requires me to process an XML file from Google. Being the lazy sort, I'd really rather just use the data as though it were part of a database and forget […]
- Multi-layer LINQ via Extension Points As promised a few days ago, I will be covering multi-layered architecture as it relates to LINQ. The first thing we need to evaluate is how Microsoft intended multi-layered architecture […]
- Sharing ObjectDataSource From Codebehind I ran into an interesting “problem” last week that wasn’t all that hard to figure out once I broke out the debugger. But I thought it would be useful to share the results to save […]
About Dave Bush