Quick Reads in the Age of Information Overload

So dig: I am trying to get rid of the small pile of full duplex, two-up, laser hard copies laying around my cube and my pad. I get intimidated and greedy when a new article comes out—especially articles covering aspects of the next release of .NET technologies. It’s time to beat down this fear and make it fit into my little fiefdom of reality where I rule with an iron paw. Meow. Hear me roar.

It’s All about DataSource Controls

Three guys from Infusion Development, Jayesh Patel, Bryan Acker, Robert McGovern, penned “Data Access in ASP.NET 2.0” for MSDN. The heart and soul of this article is made of two pieces, introducing the DataSource control and, as a consequence, introducing the new data-bound controls in ASP.NET 2.0. The ObjectDataSource thingy is quite interesting:

The System.Web.UI.WebControls.ObjectDataSource is used in scenarios where you need to implement a data access layer to provide better encapsulation and abstraction. Instead of binding to a database, the ObjectDataSource control lets you bind to a specific data layer in the same manner by which you bind to the database using other controls. The ObjectDataSource control can bind to any method that returns a DataSet or an IEnumerable object (for example, a DataReader or a collection of classes).

Great. And few paragraphs later, we find that the sequel to the DataGrid is the GridView control. Live with it.

Don’t Read about Migrating to 2.0 from 1.1, Watch the Movie Instead

You can read another Infusion Development article at MSDN, “Migrating from ASP.NET 1.x to ASP.NET 2.0,” and/or you can watch the movie, “Russ’ Tool Shed Webcast: Migrating to Visual Studio 2005 Series (Part 1 of 4): Moving from ASP.NET 1.1 to ASP.NET 2.0 (Level 200).” I’m pretty sure it was Russ that inspires the following ASP.NET 2.0 issues:

Dynamic Compilation issues: the platform will generate a random number of randomly named DLL files on the fly. This means that calls to types that do not derive from the namespaces of the platform will fail. This implies that “business logic” should be confined to a predefined folder (\app_code?) instead of scattered among ASPX files.

Debugging issues: Take advantage of Trace.Warn() and Trace.Write() to customize trace output.

The \aspnet_client folder should disappear in version 2.0. This is replaced by a custom HTTP handler that reads from a file called WebResource.axd.

Another Badly Written Article from CodeProject.com

A graduate of the University of Karachi, Sadaf Alvi, tries level best to let me know about “Attributes in C#.” For lack of another article, I depend on Sadaf Alvi for some insight. When I criticize the writing of others, there is no implication that I am the greatest writer in the world (and a bizarre racist xenophobe)—but damn!

rasx()