2. What has to re-architected in a VB 6 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

Digg This!     StumbleUpon     Del.icio.us

RELATED CONTENT VB 6 to VB .NET Migration On managing a .NET Framework 1.x migration Tool translates VB .NET code to Java Microsoft unveils VB 2005 'Power Packs' Mini-Guide: The VB.NET Development Environment, Part 3 Mini-Guide: The VB.NET Development Environment, Part 2 Mini-Guide: The VB.NET Development Environment, Part 1 Put VB.NET events in the hands of AddHandler Choosing VB.NET or C# Learning Guide Object-Oriented Programming in VB .NET Learning Guide Quiz: What do you know about VB 6 migration?

RELATED GLOSSARY TERMS Terms from Whatis.com − the technology online dictionary .NET  (SearchWinDevelopment.com)

RELATED RESOURCES 2020software.com, trial software downloads for accounting software, ERP software, CRM software and business software systems Search Bitpipe.com for the latest white papers and business webcasts Whatis.com, the online computer dictionary