数据库外文中文 毕业设计好帮手

Life after Visual Basic 6.0 – Where to Go from Here

Wendy Logan

Test Software Product Manager, National Instruments

11500 N. Mopac Expressway, Austin, Texas 78759

Phone: 512-683-9311 Email: wendy.logan@ni.com

Abstract – With Microsoft’s extended support for Visual Basic(VB) 6.0

ending this year, many application developers are looking for guidance

on whether to upgrade, reuse, rewrite, or replace their legacy VB 6.0

makes your application more compatible with future versions of VB and

gives you access to .NET features, but this option requires significant

rework. You could also stay with Visual Basic 6.0 for existing

applications that run critical tests, and then call this code from new

languages. Finally, you could replace your VB 6.0 code with code written

in another general-purpose language that supports .NET such as C++ or

C# or, you can move to one of several languages specifically designed for

test and measurement such as NI LabVIEW, NI LabWindows/CVI, Agilent

VEE, or HTBasic.

Keywords – visual basic, migration, .net.

to consolidate different code bases and software competency, reduce

upgrade and maintenance cost, ensure ongoing training and official

language support, take advantage of the latest productivity enhancements

and language features, or create or improve existing distributed

applications, using the latest Web technologies. To effectively analyze if

and which applications you should migrate to VB .NET, you must first

understand the key components of .NET, the differences between VB 6.0

and VB .NET, and your options for migrating to .NET. This article will

discuss the key elements of the .NET framework and how to integrate or

convert existing VB 6.0 applications into .NET to realize these benefits.