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


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 first published in October 2006

There are Comments. Add yours.

TIP: Want to include a code block in your comment? Use <pre> or <code> tags around the desired text. Ex: <code>insert code</code>

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy
Sort by: OldestNewest

Forgot Password?

No problem! Submit your e-mail address below. We'll send you an email containing your password.

Your password has been sent to: