Visual Basic 6.0之后的选择：升级、重用还是替换

需积分: 4 22 浏览量更新于2024-12-21 1 收藏 389KB PDF 举报

"这篇计算机专业的英文文献探讨了在Visual Basic 6.0的微软扩展支持结束之后，开发者应该如何选择前进的方向。文章由Wendy Logan撰写，她是National Instruments的测试软件产品经理，提供了对是否升级、重用、重写或替换遗留的VB6.0代码的见解，以适应支持的新软件平台。" 在微软停止对Visual Basic 6.0的扩展支持后，开发者面临一个关键的问题：如何处理基于VB6.0的应用程序。Visual Basic .NET（VB.NET）被指定为VB6.0的继承者，但它的语法更接近C++，这使得从VB6.0过渡变得具有挑战性。尽管如此，迁移到VB.NET可能会带来诸多好处，因为它允许开发者利用最新的.NET框架功能。升级或转换VB6.0代码到VB.NET是其中一种选择。这样做可以使应用程序与未来版本的VB保持更好的兼容性，并且可以访问.NET Framework提供的新特性。然而，这个过程需要大量的重构工作，可能涉及重新设计和编码。另一种策略是保持现有应用在VB6.0环境中运行，特别是对于那些执行关键任务的测试应用。这些旧代码可以继续在原环境中执行，然后通过新的语言调用这些代码，实现新旧系统的协同工作。这种方法可以降低迁移风险，但可能导致长期维护复杂性增加。最后，开发者也可以考虑替换VB6.0代码，采用完全不同的编程语言或技术栈。例如，可以转向C#、Java或其他现代编程语言，或是利用如Python、JavaScript等脚本语言。这些替代方案可能更适合开发Web应用、移动应用或云服务，能更好地适应当前的技术趋势和市场需求。无论选择哪种策略，都需要全面评估现有代码库的规模、复杂性、业务依赖以及团队的技能集。迁移过程中应考虑培训、工具、成本和时间投入，以确保决策符合长期的业务目标。同时，也要注意保持向后兼容性，以减少对用户和客户的影响。 "Life after Visual Basic 6.0 – Where to Go from Here" 这篇文章为面临VB6.0更新挑战的开发者提供了一个指导性的决策框架，帮助他们权衡各种选择的优缺点，以便在软件开发的道路上做出明智的决定。

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 code in favor of developing on supported software

platforms. VB.NET, the designated successor of VB 6.0, looks more

like C++ than traditional Basic, making the move from VB 6.0 less

than ideal – but the move may be worth the effort. To develop

applications that take advantage of the latest .NET framework, you

have three basic options: upgrade/rewrite, reuse, or replace.

Upgrading or converting your VB 6.0 code to VB .NET 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.

I. INTRODUCTION

When the .NET technology was introduced in 2002, it was

clear that it represented a significant redesign of the

underlying Visual Basic programming language. For test

applications, the new features help with writing distributed

applications, organizing large programs, and achieving

maximum performance. Engineers want to migrate to Visual

Basic .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.

II. THE BASICS OF .NET

The .NET framework includes a set of class libraries that

cover a number of common programming needs including

file I/O, database connectivity, Web application development,

and Windows services such as background printing and

integrated e-mail. One class library automatically generates

database-access objects, which you can then use to request,

update, and reconcile data between multiple data sources

without needing database programming skills [1]. There are

many other components of the .NET framework that offer

particular value to the test engineer, including ASP.NET,

Web services, and multithreaded APIs.

ASP.NET is a framework used to create interactive Web

pages that are well-suited for remote monitoring and control

applications. If the scarcity or location of test hardware

requires you to be able to remotely monitor or control a

system, creating a Web-based application may be the

solution. Because ASP.NET does not require run-time

engines to be installed on client computers, you do not need

to update each client with every new revision of the

application.

Web services are self-contained modular applications that

can publish information and be invoked across the Web. An

example Web service could make available all of the

calibration details for a transducer or instrument, eliminating

the need to manually enter that data into your PC.

Another useful .NET feature is the built-in multithreading

APIs. By using multiple threads in an application, you can

ensure that your applications will be responsive to the user

and, at the same time, be able to execute actions at regular

intervals. For instance, by isolating data acquisition (DAQ)

and user interface tasks on different threads, you can ensure

that user interface updates will not be delayed by calls to the

DAQ hardware and vice versa.

A. .NET Common Language Runtime

When choosing a development language for a new

project, many factors usually come into play including

personal preference and expertise, legacy code, and internal

and external support for the language. Because certain

languages may be appropriate for particular projects, many

companies have to maintain code bases that include

programming languages with different features and data

types. The .NET framework was designed to help address the

challenge of supporting systems written in different

programming languages. Instead of compiling directly down

to native machine code, VB .NET code, for example, is

compiled into an intermediate language called the Common

IEEE AUTOTESTCON 2008

Salt Lake City, UT, 8-11 September 2008

Authorized licensed use limited to: CHINA UNIVERSITY OF MINING AND TECHNOLOGY. Downloaded on May 31, 2009 at 05:01 from IEEE Xplore. Restrictions apply.

下载后可阅读完整内容，剩余3页未读，立即下载

wangxinall

粉丝: 1
资源: 18

Visual Basic 6.0之后的选择：升级、重用还是替换

"Visual Basic语言和算法翻译及文献综述PDF文件

CellSim (Game of Life)-Visual Basic实现的生命游戏开源项目

Windows平台下用Visual C++实现堆栈版Life游戏

Life after Google

fcfs-master.zip_C#_fourthunl_inchmaa_visual basic_yes

life-after-hate:直观的资源图可帮助非营利组织Life After Hate员工为试图摆脱仇恨团体的个人寻找资源

Life After BerkeleyDB- OpenLDAP's Memory-Mapped Database

Life-after-BrainStation

life-after-selenium

recorder:一个简单的记账本，可以记录我的花费，帮助我知道自己把钱花在哪了。 An easy notebook , a website can record any payments from my daily life, and help me know where I pay

最新资源