My Rants and Raves about technology, programming, everything else...
I seem to be getting a lot of questions and reviewing a lot of code that isn't use TableMappings and I wonder why. For example I see this occassionally:
DataSet ds = new DataSet();
SqlDataAdapter da = new SqlDataAdapter();
// Setup Adapter here ds.Fill(ds);
ds.Tables["Table"].TableName = "Customers";
The problem here is that you don't even need TableMappings, you could call the fill like so:
I just got back from seeing Constantine. The first movie I've went out to see on the opening weekend in quite a while. Overall, it was a fun ride. I do recommend it, but just don't expect a new "Matrix" or anything. There are some theological inconsistencies, but in general great performances all around (even Reeves, but don't quote me on that). Terrific visuals too.
I've been spending some time lately reviewing how companies are doing data access in .NET. When I look at how most of them have crufted up solutions, I am amazed. The model that Microsoft supports seems so obvious to me, but I am neck deep in it. I'd like to hear from my readers their specific experience with creating data access in .NET; with an eye to why or why not use COM+ for transactions; Typed DataSet or DataReaders; Business Objects or Messages. I am trying to understand where the community is.
Thanks in advance...