Greg Robinson's Blog

I have spent the past 2 days trying to figure all of this out.  Our app DataBinds to many data sources, all ADO.NET types.  Mostly from one dataset, but in some cases, like our drop downs that load from a code table, they are not related. 

I have been working on a generic helper class that, among other database services, will take a modified dataset that contains multiple modified datatables and do an update.  Long story made real short, all worked well on the first DataTable update, but not the following ones.  The Command was getting built correctly, however I kept getting exceptions that informed me the parameter passed in was not a member of the stored proc (the code builds the sproc name dynamically per the Datatable info).  

I have not blogged for quite some time.  We have been very cranking out code.  I have learned a ton lately.  Cool stuff I have learned:

I just read where we now have Intellisense in the Debug|Immediate window with v 1.2.  Too cool.  I have had this on my wish list for quite some time. 

My thing today is questioning the typical model of passing data between logical tiers as result sets, xml, arrays, strings, etc.  This Microsoft article does a nice job outlining other options.

Standard, out of the box .NET collections store references of type System.Object.  We have a structure that we add to a collection.  We add approx 2500 structure types to this collection.

I come from a vb background.  I am the classic business dude who later in life developed an interest in programming.  I guess I am a Mort, although I truly do not know the definition of a mort.  Unlike a Mort though, I am more of a 'why and how does this work', so I love vb.net, however I like to dig into the framework and the internals of what .net is doing for me. 

 Picking VB.NET over C# is a little like picking which Playboy bunny will join you in the hot tub—you can’t go wrong either way.