Re: ADO.NET vs ADO

Michel,

Scott is as well a long time contributer too the ADO.Net newsgroup, like Bill Vaughn, in past David Sceppa and I.

Cor

"Michel Posseth [MCP]" <MSDN@xxxxxxxxxxx> wrote in message news:%23hTMJCuMJHA.4772@xxxxxxxxxxxxxxxxxxxxxxx


I had not so much trouble adopting ADO.Net and have never written anny ADODB code in a .Net environment
and that while my first coding experiences where in the mid eighty`s on a CBM64 .

I honestly believe that anny coder can be up and running with ADO.Net in just a few hours you just need a good coding reference
so do yourself a favor and buy yourself a good ADO.Net reference book . I would recomend you the following writers Bill Vaughn , Francesco Balena , David Sceppa .


And if you encounter anny problems you can`t solve yourself there is always someone here in these groups for assistance


regards

Michel Posseth
http://www.vbdotnetcoder.com






"Scott M." <s-mar@xxxxxxxxxxxxx> schreef in bericht news:eMdbiKtMJHA.4600@xxxxxxxxxxxxxxxxxxxxxxx
Others have mentioned some good resources, but I'd like to address the benefits of ADO .NET vs. the pitfalls of ADO.

First, using ADO in .NET will inherantly cause performance problems as you will be utilizing COM architecture in .NET. So, right away you are at a disadvantage and will never see the best performing code you could have using ADO in .NET.

Second, ADO was, by default, a "connected" paradigm and while you could indicate you wanted to work with client-side cursors, it made the coding much more complex.

Third, ADO was very limited in the kinds of operations you could perfom on / with your data (ie. one RecordSet was isolated from another).

ADO .NET is all about working with disconnected data, by default, with some very good options available for working in a connected mode. It has a very heirarchical model, which follows the logical structure of a relational database.

Sure, because the model is bigger, it can also be more complex than ADO, but that doesn't mean ADO is better.

My advice, when moving to .NET from the "classic" technologies is, honestly, to forget what you know and approach .NET programming as a completely new paradigm. If you try to learn .NET from a standpoint of "How does this releate to what I already know?", you will invariably get a brain-cramp.

-Scott

"Kevinp" <kevinp@xxxxxxxxxx> wrote in message news:4i9if41c7crojv10pkhmt9v8hp4o2dk1fg@xxxxxxxxxx
Just a silly question probably...

I made the switch from VB6 to VB2005 when 2005 came out. Now I'm using 2008. When I started programming, VB5 was just out and I was using RDO. I loved ADO when it came out and quickly switched all my programs to use it.

I've tried to make the switch to ADO.NET, but just can't seem to figure out what I'm doing most of the time. I'm using it in just a couple of forms where I needed it to work with a DataGridView and to update a few records.

Am I the only stupid one out there that would rather use the old ADO? Is there an easy way to learn ADO.NET?





.