Convert ADODB to ADO.NET? Will it provide a big increase in speed?

Visual Studio 2005.  .NET 2005 VB.NET  ASP 2.0

I need to convert some ADODB code to ADO.NET.  What are some good sources that show why ADO.NET is better.  And how to go about converting ADODB to ADO.NET.  The ADODB code is pretty sloply and needs to be cleaned up anyway, so I figure I should also upgrade to ADO.NET.  It is a VB.NET 2.0 Application, but the programmer still used old ADODB.

Like converting ADODB.Recordset to the equivalent in ADO.NET
EpicmanagementAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

dqmqCommented:
I would say ADO.NET is a radically different paradigm.  So much so, ADO.NET does not have a recordset equivalent, though it still comes with data providers that are backward compatible with the ADODB objects. So, be prepared for a pretty big learning curve and substantial re-write if you really want to make the leap completely.

A highly recommended source is "ADO.NET 2.0 Step by Step" from Microsoft Press. And some classes--it's a pretty tough transition by the seat-of-your pants.  

0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
EpicmanagementAuthor Commented:
Is it worth doing the conversion.  Is there any performance increase.

I am not new the ADO.NET, I've used it for executing StoredProcedueres and inline SQL, and the code I am working with is not opimized at all.  For example, rather than having stored procedures that accept paramaters, the code has lots of inline sql.  I have to make lots of changes anyway, so I was just wondering if it is also worth converting to .NET.
0
planoczCommented:
You need to get the programmer to upgrade his knowledge  able .NET and ADO's or get a new proprammer.
After being in programming from VB4 to .NET I would never go back to VB6, etc. .Net is the way to go there is alittle time needed for learning.
0
grayeCommented:
As others have already pointed out, an automatic "conversion" to ADO.Net is probably not a good idea.

There is a significant "paradymn shift" (I hate using management-speak buzzwords) between the "old" way to do things things and the "new" way.   A mere "conversion" doesn't do it.  It's almost always requires a complete re-write.

As for performance... you're probably not gonna like this... No, it's not an improvement

But, that's not all bad... somethings it does very well, but as for "raw database performance"... sorry.   On the other hand, ADO.Net is a blessing for the database backend... you should see a drop in processor/memory load on the database server.

Having said all of that, I'd *still* recommend that you convert (as soon as possible) to VB.Net 2005 way of doing things
0
dqmqCommented:
>Is it worth doing the conversion.
I would say, estimate the costs, estimate the benefits, then decide.

The good news is that's it's not an all-or-nothing proposition.  You can do a little bit, see how it goes, and then make an informed choice.


 

0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
.NET Programming

From novice to tech pro — start learning today.