ASP.NET 4 adds a wealth of features for client-side developers, including new ways of instantiating controls, a new infrastructure for managing libraries and some minor but much-needed tweaks. And there's more.
Peter considers two solutions for keeping items in the sitemap off of your Menu or TreeView controls. But he's also wondering if there are more solutions out there.
Peter Vogel closes out his eight-part series on creating an AJAX-enabled ASP.NET application.
Peter moves on from working with one record to working with multiple records and explores Microsoft's current templating solution.
Peter moves on from simply retrieving data from the server using the dataContext and dataView to doing updates, deletes and inserts.
Continuing his investigation of what works and doesn't work with the AJAX library and .NET 4, Peter Vogel continues to explore how to retrieve data from the client... and discovers that it can be very easily done.
Peter Vogel discusses what you can't do in marrying ASP.NET server-side controls with client-side data access.
Peter uses the new dataView and dataContext objects from the AJAX Toolkit to create a data-driven page without server-side code.
If you want to integrate server-side Web service processing with AJAX objects in your browser, you should be considering WCF Data Services -- especially if you're working with the Entity Framework. Here's a quick introduction to the technology.
Peter Vogel returns to creating an AJAX-enabled ASP.NET application using the latest tools out of the AJAX library and .NET 4. However, it turns out that you can't there from here... at least, not right away.
Peter Vogel wraps up coverage of object-oriented programming for the single-tier developer by handling the difference between the data required by users and the object used by the business layer.
If you're going to use the ObjectDataSource in a real application, you'll need to support all of the CRUD activities. Peter Vogel extends his object model to do just that.
Peter Vogel continues to look at the basics of O-O development to support the ASP.NET ObjectDataSource.
You're considering the ObjectDataSource but you're not an object developer. Peter Vogel shows you what you need to do to move into multi-tier development.
You put all of your code in the code file of your ASP.NET pages -- but other developers keep kicking sand in your face because you're not doing n-tier development. Peter's here to say that you're not (necessarily) being dumb.