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.
Adding some bizarre punctuation marks to the tags in your ASPX file gives you an easy way to move data out of custom properties and into your page.
Create a virtual page handler that lets you deliver data directly from your database to your Web users. The handler also lets you move your app into the world of REST Web Services.
Creating your own HTTP handler in ASP.NET 1.1 or 2.0 gives you a flexible and fast way to move data to clients, browsers, and other Web pages.
It's not enough to build a great custom control to help your end users -- you must also help other developers use your control.
Learn how to integrate ASP.NET's built-in security tools with the features of your existing site.
ASP.NET 2.0 provides a robust set of functionality for implementing rich and flexible forms authentication in your applications.
Microsoft's Atlas toolkit for building Ajax-enabled applications allows you to create more interactive and more scalable application than conventional Web tools-and even outperforms .NET smart client applications.
Take advantage of these performance tips, and make your ASP.NET applications fly whether you use version 1.1 or 2.0.
Databinding in ASP.NET 2.0 is a different beast from its original implementation in ASP.NET -- there are more databinding controls and a radically different approach that gets more done with less code.