2. What has to re-architected in a VB 6 migration?

Some bits of a Visual Basic 6 application, like most APIs, can be easily migrated to VB.NET; other parts are not so straightforward. Which of the following will NOT have to be re-architected during a VB 6-to-VB.NET migration?

2. Some bits of a Visual Basic 6 application, like most APIs, can be easily migrated to VB.NET; other parts are not so straightforward. Which of the following will NOT have to be re-architected during a VB 6-to-VB.NET migration?
A) DHTML pages
B) ActiveX documents
C) OLE controls
D) ADO to ADO via Interop

ANSWER: D

A VB.6 migration is not entirely smooth sailing, said Keith Pleas in the SearchVB.com article, Webcast: How to upgrade legacy VB 6 applications. .NET Framework transactions must be done manually, while items like ActiveX documents, DHTML pages and OLE controls need a bit of re-architecting. ADO to ADO via Interop data access migration, though, is pretty straightforward.

Return to the answer page
Return to the quiz

This was last published in October 2006

Dig Deeper on VB 6 to VB .NET Migration

Start the conversation

Send me notifications when other members comment.

Please create a username to comment.

-ADS BY GOOGLE

SearchCloudComputing

SearchSoftwareQuality

TheServerSide.com

SearchCloudApplications

Close