Preparing Your Visual Basic 6.0 Applications for the Upgrade to Visual Basic .NET Overview This document provides recommendations for developers using Microsoft® Visual Basic® who are planning to upgrade their applications to Microsoft Visual Basic .NET.32357
Visual Basic .NET will open and upgrade Visual Basic 6.0 projects to Visual Basic .NET technologies, but in most cases you will need to make some modifications to your projects after bringing them into Visual Basic .NET. The purpose of this document is to recommend how to design and implement your current Visual Basic projects to minimize the number of changes you will need to make when they are upgraded to Visual Basic .NET. Where appropriate, we use new language constructs; however, this document is not intended to be a Visual Basic .NET language reference.
What Is Visual Basic .NET?   
Visual Basic .NET is the next version of Visual Basic. Rather than simply adding some new features to Visual Basic 6.0, Microsoft has reengineered the product to make it easier than ever before to write distributed applications such as Web and enterprise n-tier systems. Visual Basic .NET has two new forms packages (Windows Forms and Web Forms); a new version of ADO for accessing disconnected data sources; and streamlined language, removing legacy keywords, improving type safety, and exposing low-level constructs that advanced developers require.
These new features open new doors for the Visual Basic developer: With Web Forms and ADO .NET, you can now rapidly develop scalable Web sites; with inheritance, the language now truly supports object-oriented programming; Windows Forms natively supports accessibility and visual inheritance; and deploying your applications is now as simple as copying your executables and components from directory to directory.
Architecture Recommendations   
The .NET platform improves upon previous architectures, and adds greater support for scalability and distributed applications though disconnected data access, HTTP-based message transport, and file-copy based deployment (no more registering of components). To best take advantage of these features, you should design your applications with an architecture similar to that you would use in Visual Basic .NET.
Upgrading
When your code is upgraded, Visual Basic .NET creates a new upgraded project and makes most of the required language and object changes for you.
Visual Basic Forms to Windows Forms
Visual Basic .NET has a new forms package, Windows Forms, which has native support for accessibility and has an in-place menu editor. Your existing Visual Basic Forms are upgraded to Windows Forms.
Interfaces
In previous versions of Visual Basic, interfaces for public classes were always hidden from the user. In Visual Basic .NET, they can be viewed and edited in the Code Editor. When your project is upgraded, you choose whether to have interface declarations automatically created for your public classes.
Upgrade Report and Comments   
After your project is upgraded, an upgrade report is added to your project, itemizing any changes you will need to make to your upgraded code. Additionally, comments are added to your code to alert you to any potential problems. These comments show up automatically in the Visual Studio .NET Task List.
Programming Recommendations
This section provides recommendations for how you should write code to minimize the changes you will need to make after upgrading your project to Visual Basic .NET.
Use Date for Storing Dates
Earlier versions of Visual Basic supported using the Double datatype to store and manipulate dates. You should not do this in Visual Basic .NET, because dates are not internally stored as doubles.
B.原文的翻译
准备将 Visual Basic 6.0 应用程序升级到 Visual Basic.NET
概述   
本文档为使用 Microsoft® Visual Basic® 的开发人员提供有关将应用程序升级到 Microsoft Visual Basic.NET 的建议。 VB程序设计英文文献和中文翻译:http://www.youerw.com/fanyi/lunwen_28889.html