What's in SP1 for ASP.NET developers? At least one bug fix, a couple of enhancements and -- perhaps -- something that will change your life. But Peter is suspicious.
Peter shows you how to make a Master-Detail page that will work right and save your users a lot of grief.
Peter stumps for the Cache, despite developers' worries over stale or lost data.
The ASP.NET Cache object could be the secret to speeding up your application if you just started using it more.
Peter answers a reader's question by showing how to access data inside the individual controls of the various DataViews.
Want to give your users personalized pages without giving up control? It's easy with Web Parts. Peter shows you how.
Moving from a test to a production environment can be tricky. Here's where the Web Deployment Projects add-on comes in handy.
Peter shows a "code-lite" way to handle exceptions when using DataView to update data.
This is one big problem that's simple to fix. Peter shows you two solutions.
Seriously, don't. Here are two reasons why record locking is simply a bad idea.
Optimistic concurrency doesn't work for most tables, but Peter shows you how to change that.
Client-side debugging is better, but IntelliSense still has a few issues to be worked out.
Peter shares what he likes -- and doesn't -- in Visual Studio 2008 and ASP.NET 3.5
It's good news, bad news if you're upgrading an existing site to ASP.NET 2.0 or 3.5. But it can be done.
In theory, PreviousPage lets you access data on the page the user just requested. In practice it doesn't work if you're also using Master Pages unless you understand ASP.NET naming containers.