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.
Microsoft ASP.NET Senior Program Manager Stephen Walther Talks with Peter Vogel about jQuery, AJAX and ASP.NET 4.
Peter continues his exploration of the new Routing features in ASP.NET 4 by showing how to bind control properties to both routes and the values passed in a route.
You may have noticed that more and more sites have URLs that mean something rather than describing the path to the page. ASP.NET 4 makes this much easier to implement for your site and may save you from ever having to redirect users again.
If you're using the ASP.NET Cache object, then somebody is suffering when you first load the Cache. Here's how to avoid that and, potentially, save a bit of money while you're at it.
Peter starts looking at the new features in ASP.NET 4, starting with support for compressing Session data and setting up permanent redirects.