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.
Having looked at how to prepare an e-mail object, Peter turns his attention to getting the message mailed to someone.
The MailMessage object that's part of .NET lets you send e-mail notifications to your users and supports all the customizations you'd want in e-mail.
Peter returns to the topic of user interfaces to explain why you shouldn't waste any time helping your "expert" users -- and what you should be doing instead.
Set aside ASP.NET for now. Let's talk about the most fundamental error developers make in designing their site's user interface.
To fully exploit User Controls, you need to treat them as object -- which includes having them fire events. If firing your own events is new to you, here's a step-by-step guide.
ASP.NET developers don't fully exploit User Controls -- until they start thinking of them as "User Interface" objects.
All you need to let your users customize their Web pages is the ability to create UserControls.
Peter continues his series on integrating cascading DropDownLists with databound controls. But this time, he looks at what's different when you're using the ObjectDataSource.