migrating vb6 code using adodb

[Peter]

I am involved in migrating a sizeable vb6 application to vb.net but don't
want to add the extra complexity of migrating adodb to ado.net. Is this a
sensible approach and if not what are the drawbacks?

 

[Norman Yuan]

There isn't a something/tool that can reasonablly good enough to convert a
real, sizeable VB6 app to a good .NET app (win form app or web app?). Most
likely the conversion means total re-writing after all. So, if you
converting/rewriting, why not doing it the .NET way? If I were you, I'd
either not do it at all, or do it the .NET way, if the app is important to
the business enough that is worth the converting, I mean, re-writing.

 

[sloan]

IMHO...it's a horrible decision to use ADO instead of ADO.NET.

They are nothing like, except in an acronym.

The migration tools will convert the code to ADODB objects...but it is very
out of place.

...........

If I had a sizable VB6 to convert...I'd spec it out and rewrite it.
Maybe some of the modules can go into classes....but other than that....I'd
advise a rewrite..as soon as possible.
And in (at least) .Net 2.0.

Your other option is to find another job.


Good luck.

 

[Peter]

I know it sounds horrible, but is there really a good reason to get extra
budget to migrate the adodb code. I could do with some real facts about it to
aid my case!

I have seen some people mentioning performance benefits of ado.net but not
found any solid evidence either way (i.e. will I get a performance
degradation leaving adodb there?). I also went on a .net migration course and
the tutor implied that it was not a make or break decision to leave the adodb
code there!