vb.net upgrade: ADODB Reference Required -- vb.net upgrade

RE: ADODB Reference Required

JohnHart NO[at]SPAM Online.Microsoft.com.
1/22/2005 1:36:19 AM

Hi Vic,

Which version of VB.Net are you using? Did the Upgrade Wizard add the
reference to ADODB for you or did you add it?

If you expand the References in the Solution Explorer do the properties for
ADODB look simular to:

Description: Microsoft ActiveX Data Objects 2.8 Library
Identity: {2A75196C-D9EB-4129-B803-931327F72D5C}\2.8\0\tlbimp
Path: ...\obj\Interop.ADODB.dll

If you reference is different I would try removing the reference and adding
one manually through the Add Reference dialog

--
John Hart, Microsoft VB Team
This posting is provided "AS IS" with no warranties, and confers no rights.
--------------------
[quoted text, click to view]
cpmsftngxa10.phx.gbl!TK2MSFTFEED02.phx.gbl!tornado.fastwebnet.it!tiscali!new
sfeed1.ip.tiscali.net!news.tele.dk!news.tele.dk!small.news.tele.dk!enews.sgi
com!msrnewsc1!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP09.phx.gbl
[quoted text, click to view]

Re: ADODB Reference Required

Vic Spainhower
1/26/2005 12:39:49 PM

John,

Thanks for the reply and sorry I didn't respond sooner but I decided to
abandon the VB6 conversion tool and manually convert this program. But to
answer your question the reference was automatically and was as you had
stated. I didn't like all the "extra" stuff added by the conversion tool and
felt the time to weed out all of the problems it appears to have would be
better spent on just manually converting the app.

I've read a number of posts that the conversion tool most of the time does
not work, is this true? BTW I am using the standard version of vb.net.

Thanks,

Vic

[quoted text, click to view]

Re: ADODB Reference Required

JohnHart NO[at]SPAM Online.Microsoft.com.
1/27/2005 1:40:39 AM

The Upgrade Wizard for most medium to large projects is not going to be
able to upgrade 100% of the Vb6 code. So when you read that the upgrade
tool isn't working I expect that most the time this is because it was
expected to upgrade the application perfectly.

Now I'm also not saying that the tool doesn't run into problems at times
because it does as in you've unfortunetly found out. I do believe that
using the tool is an excellent way to get most of your application upgraded
and in most cases this will be more cost effective then converting the
program manually.

I know you've worked around the ADODB problem but I would like to learn
more about the issue so that we can help others that might run into the
problem and fix it. Is it possible for you to send me a project that
reproduces it the problem? I haven't been able to reproduce it here.

If so you can send it to JohnHart@Microsoft.com

Thanks and I'm sorry you ran into problems.

--
John Hart, Microsoft VB Team
This posting is provided "AS IS" with no warranties, and confers no rights.
--------------------
[quoted text, click to view]
cpmsftngxa10.phx.gbl!TK2MSFTFEED02.phx.gbl!tornado.fastwebnet.it!tiscali!new
sfeed1.ip.tiscali.net!news.maxwell.syr.edu!logbridge.uoregon.edu!arclight.uo
regon.edu!enews.sgi.com!msrnewsc1!TK2MSFTNGP08.phx.gbl!tk2msftngp13.phx.gbl
[quoted text, click to view]

Got something to say? Click here to post a reply to this thread.

Don't see what you're looking for? Try a search.

View other messages in the vb.net upgrade group.