ScottGu's Blog

Last weekend I posted about how to implement super efficient data-paging using the new ROW_NUMBER() within SQL 2005 (which is supported with the free SQL Express edition and up) and the new ASP.NET 2.0 GridView/ObjectDataSource controls.

Rick Strahl has posted a good example on his blog about how to programmatically configure ACLs and permissions for things like files and directories using the new .NET 2.0 filesystemaccess APIs.  Worth taking a look if you are looking to automate the setup of ACL permissions as part of a setup script/program.

Dave Wanta has created an awesome site dedicated to all things relating to System.Net.Mail -- the new email API that ships with .NET 2.0. 

I stumbled upon this blog post earlier today that I thought was pretty cool.  It describes a pretty easy way to add confirmation pop-ups for delete command (or update or edit or any other command) using a GridView control, or before any other post-back event in ASP.NET.  It takes advantage of the new "OnClientClick" property that button controls now have in ASP.NET 2.0 -- and which allow you to author client-side event handlers that can fire prior to post-back (you return true or false from these javascript handlers to indicate whether you want the post-back to continue).

One complaint I've heard a lot is the performance of the new C# refactoring feature with web pages in VS 2005.  VS 2005 added support for enabling refactoring everywhere (for example: even within <% %> blocks defined inline with a .aspx page), which is nice from a feature-completeness perspective.  The problem, though, is that by checking every file and possible context, it can end up slowing down performance considerably.  The more pages you have in a project, the slower and slower refactoring gets (to the point of being unusable).

David Hayden blogged about a cool new ROW_NUMBER() function that SQL 2005 provides that got me excited and inspired to write a little code last night.

K. Scott Allen recently published a good post on the new ASP.NET 2.0 Profile system.  The profile system provides an easy way to store and retrieve properties about users on your sites -- both logged-in and anonymous.  It can save you time and effort in providing a richer personalized experience for people using your site.

In case you haven’t checked out the new Atlas preview release yet (which given that it shipped a few days ago and almost everyone is on vacation this week is very likely), you might want to consider finding some time to-do so when you get a chance and are back online.  It makes common Ajax-style scenarios a breeze to build, and really makes programming a lot of fun.