Peter adds the code to support doing updates and deletes with an unbound GridView.
If you want to let your users edit repeated rows of data, you can use the GridView -- even if your data isn't in a table. You need to do pick the right design for your data but you can enable all of the functionality of the GridView for data held in memory.
Sorting in the GridView is simple to implement, as long as you want simple sorting. For more complex sorts you have to take control of the Sorting event.
Peter returns to .NET RIA Services to look at the client side of creating an application.
The ASP.NET-related portions of .NET RIA Services aren't ready for primetime yet, but now's a good time to start kicking the tires.
Your users may want to get their data in a specific order -- and not get it all at once. You can control both with the ObjectDataSource (and a little code).
Not content with providing a solution for displaying information from the Content page on its MasterPage, Peter returns to the topic to solve the problem from another direction.
Validator controls make handling errors and reporting them in the UI easy, but what you may not know is how easy it is to create your own Validator.
In his ongoing campaign to convince ASP.NET developers that User Controls are a simple way to start implementing customizable pages, Peter shows how to improve the integration between User Controls and ASP.NET's WebPart framework.
If you're concerned about keeping critical information in your Web.config file, then you should encrypt it -- or at least the parts that you're concerned about.
If you want to use Entity Framework in ASP.NET, you're going to need to handle concurrency problems. Here are some suggestions from a Microsoft "architect evangelist."
Peter revisits the problem of dealing with multiple updates to the same data, but this time he looks at a solution that involves the ObjectDataSource.
In the last installment of this three-part series, Peter overcomes the final obstacle before achieving JavaScript nirvana: attaching a constructor to a JavaScript "item."
Peter continues to explore the differences between the .NET object-oriented, server-side languages he's used to and the world of JavaScript.
Peter has been experiencing culture shock as he adapts to working with JavaScript, starting with the discovery that JavaScript isn't an object-oriented language.