项目管理外文翻译

1、外文文献原文：Ready to upgrade Visual Basic 6.0 applications to Visual Basic.NET OutlineThis document is to use Microsoft ® Visual Basic ® developers to provide the application to upgrade to Microsoft Visual Basic.NET recommendations. Visual Basic.NET can open the Visual Basic 6.0 projects to Vis

2、ual Basic.NET upgrade its technology. However, in most cases, the project to upgrade to Visual Basic.NET, you need to make some changes to the project. The purpose of this document is on the design and implementation of the current Visual Basic project to provide recommendations to upgrade to Visual

3、 Basic.NET only after a minimum of changes. Where appropriate, we will use the new language structure; However, this document is not a language reference for Visual Basic.NET. What is Visual Basic.NET? Visual Basic.NET is the next version of Visual Basic. Microsoft re-designed the product, rather th

4、an simply as Visual Basic 6.0 add some new features. The new version easier than previous versions of the preparation of distributed applications, such as Web and enterprise n-tier system. Visual Basic.NET with two new forms packages (Windows Forms and Web Forms); used to access the disconnected ADO

5、 data source for the new version; the latest model of the language, remove the traditional keyword, improved type security and advanced developers need to open a low-level structure. These new features for the Visual Basic developer opened a new door: Use the Web Forms and ADO.NET, to rapidly develo

6、p scalable Web sites; through the inheritance, the language can be a real object-oriented programming support; Windows window body itself to support access and visual inheritance; now deploy your application as the executable files and components from one directory to another directory so simple. Vi

7、sual Basic.NET is now available in other languages fully integrated with Microsoft Visual Studio.NET. You can not only use different programming language to develop application components, and your class can now cross-language inheritance to inherit classes written in different languages. Using the

8、unified debugger can now debug multiple language applications, regardless of whether they are run locally or on a remote computer. Finally, no matter what language you use, Microsoft. NET Framework is the Microsoft Windows ® and Internet provides a rich API. Why not 100 percent compatible with

9、Visual Basic.NET? Visual Basic.NET can be designed to consider two options: Update to the existing code base. NET framework to run; or build from scratch to fully leverage the platform's advantages. To reach the customers most in need of features (such as inheritance and Threading), to provide t

10、he platform for full and unrestricted access, and to ensure the next generation of Visual Basic can access Web application, the right decision in the new platform the generation from scratch. For example, in Windows Forms in a number of new features can be used as new controls or more properties to

11、add to the existing code base. However, this will put all other important functions (such as security and visual inheritance) the cost of succession to the Windows form. Our main goals is to ensure that the Visual Basic code can be completely and use of other languages (such as Microsoft Visual C #

12、, or Microsoft Visual C + + ®) write code to work, and to Visual Basic developers easy to use. NET Framework features without using the traditional Windows API programming tools to make work. And Visual C + + and any other common language runtime to target the same language, Visual Basic now ha

13、s the same variable type, array, user-defined types, classes and interfaces; but we have removed from the language of certain functions, For example, an array of fixed-length strings and non-zero. Visual Basic is now a true object-oriented language; some non-intuitive and inconsistent feature has be

14、en removed from the language, such as GoSub / Return and DefInt. The result is a Visual Basic more dynamic, it will continue to be Windows-based application that creates the best tools, and now to create the next generation of Web site to be the best tool. Upgrade to Visual Basic.NET Visual Basic.NE

15、T from the basic principles of the traditional Windows development to build next generation Web and n-tier applications. Therefore, you need to upgrade the code to use the advantages of Visual Basic.NET. Open in Visual Basic.NET in Visual Basic 6.0 project, it will automatically appear, "Upgrad

16、e Wizard" to guide you through the upgrade process, and automatically create a new Visual Basic.NET project (your existing project will not change). This is a one-way process; in Visual Basic 6.0 can not open a new Visual Basic.NET project. Works after the upgrade, language change due to syntax

17、 changes, your form is converted to Visual Basic 6.0 Windows Forms. In most cases, the upgrade code also need to be some changes. This is because certain objects and language features in Visual Basic.NET is not equivalent to the content, or for automatic updates, the equivalent content differences t

18、oo. After the upgrade, may also need to change your applications to use Visual Basic.NET some of the new features. At the same time using Visual Basic 6.0 and Visual Basic.NET Visual Basic.NET support for Visual Basic 6.0 upgrade project; If you have a Visual Basic, version 1 to version 5, the prepa

19、ration of the project, we recommend that you load it into VB6 (the choice to upgrade Microsoft ActiveX ® controls), compile and save the project, and then upgrade the project to Visual Basic.NET. Visual Basic.NET and Visual Basic 6.0 can be installed on the same computer and run. Similarly, wit

20、h Visual Basic.NET and Visual Basic 6.0 applications written can also be installed on the same computer and run concurrently. Components written using Visual Basic.NET with earlier versions of Visual Basic, and COM components written in other languages to work together. For example, can be written u

21、sing Visual Basic 6.0 ActiveX controls to Visual Basic.NET Windows Forms drag and drop, use Visual Basic.NET Class Library in Visual Basic 6.0 COM objects, or to Visual Basic 6.0 executable file to the Visual Basic.NET Library. Components with Visual Basic.NET compiler and compiled using Visual Basi

22、c 6.0 runtime components are slightly different. For the initial application, as Visual Basic.NET objects through garbage collection release, so if the object is explicitly removed from memory before they actually delete, may be a delay. Other differences, such as variant / object changes will note

23、later in this article. A result of these differences is a common application with Visual Basic.NET Visual Basic 6.0 application running with similar characteristics, but not identical. In addition, Visual Basic.NET to Visual Basic.NET and Visual Basic 6.0 components in between these components do no

24、t binary compatible. Components are now more powerful than before, version management and deployment system, you can simply copy files to a directory (no longer RegSvr32) to deploy the file, and upgrade to new version of the component as a new file to replace the old files as easy. You have to do is

25、 to ensure that classes and methods compatible with earlier versions. Architecture proposed. NET platform on the improvement of early architecture on the scalability of distributed applications and to provide more powerful support, although it has disconnected data access, message-based HTTP-based f

26、ile transfer and deployment (no longer is a component registration). To take full advantage of these features in the design of your application architecture used, should be used in Visual Basic.NET similar architecture. Browser-based applications Visual Basic 6.0 and Microsoft Visual Studio ® 6

27、.0 to create a browser-based Internet and Intranet applications provide the following types of technologies:· Webclass· DHTML project· ActiveX Document· Active Server Pages (ASP) Visual Basic.NET introduces an enhanced version that is ASP ASP.NET, and with the Web form to the arc

28、hitecture, Web form is the case with Visual Basic HTML page. Architecture is based on the server. The following recommendations and a list of the main architecture proposed for the development of browser-based Visual Basic 6.0 applications to enable them to seamlessly migrate to Visual Basic.NET pro

29、jects: Recommend that you follow Microsoft guidelines for multi-tier architecture to create your application, using ASP to create interfaces using Visual Basic 6.0 or Visual C + + 6.0 COM object to create business logic. Visual Basic.NET in full support of ASP, you can use ASP, ASP.NET and Web Forms

30、 applications to continue to expand. Visual Basic 6.0 and Visual C + + 6.0 business objects can not be modified or upgraded to for Visual Studio.NET or Visual Studio.NET. DHTML applications, including DHTML page and the client DLL. These applications are not automatically upgraded to Visual Basic.NE

31、T. We recommend that you leave these applications in the Visual Basic 6.0. Visual Basic.NET does not support ActiveX documents, the same as the DHTML project does not automatically update. We recommend you to stay in the ActiveX document application in Visual Basic 6.0, or possible, to replace the A

32、ctiveX user control documents. Visual Basic 6.0 ActiveX documents and DHTML applications with Visual Basic.NET technology work together. For example, you can navigate from a Visual Basic.NET Web Forms to Visual Basic 6.0 DHTML page, and vice versa. Visual Basic.NET is no longer a Webclass. Webclass

33、application will be upgraded to ASP.NET, but after the upgrade you need to make some modifications. Webclass existing applications with Visual Basic.NET Web Forms and ASP applications work together, but for new projects, we recommend that you use with Visual Basic 6.0 business object ASP's Windo

34、ws DNA platform. Client / server project Visual Basic 6.0 to provide for creating client / server application of the following technologies:· Visual Basic form· Microsoft Transaction Server (MTS) / COM + middle tier objects * User Control Visual Basic.NET has a new form package, or Windows

35、 Forms. Windows Forms and Visual Basic 6.0 form with a different object model, but most are compatible. When you upgrade project, Visual Basic form is converted to Windows Forms. Visual Basic.NET development to improve the middle layer of MTS and COM + Component Services components support. Using th

36、e unified debugger, you can access from the client application MTS / COM + components, and then returned to the client application. You can also use single step debugger to debug Visual Basic 6.0 MTS / COM + components (assuming the cost of these components are compiled machine code with symbolic de

37、bugging information and no optimization). Visual Basic.NET also introduced a new middle tier components, namely Web services. Web Services in ASP.NET, and allowed through the firewall using the HTTP transport protocol request method. They use industry-standard XML data transfer and return, allowing

38、access to their other language and platform features. Although they do not support the MTS transaction, but when you do not need distributed transactions, but still need to work with other platforms, you can put MTS / COM + components into Web services. Although there is no automatic way, but this t

39、ask is very small, can be upgraded to Visual Basic.NET project, use the drag and drop in a very short time. Works upgrade, upgrade to Windows controls user controls; but the custom attribute tags to set up and assign shortcut keys will not upgrade. Single application Visual Basic 6.0 supports the fo

40、llowing types of single-generation applications: * Single-database application· Visual Basic add-ins * Tools programs and games Single database application, some Visual Basic applications, which is characterized in the Microsoft Access database to store data. These applications when upgrading t

41、o Visual Basic.NET certain restrictions (see later in this document, "data" section). Visual Basic.NET IDE is now fully integrated into the Visual Studio.NET IDE, Visual Basic.NET language center expansion with a new model. Visual Basic.NET Visual Studio.NET add-in is now the add-ins, you

42、can in any language in Visual Studio.NET automatically processed and added functionality. For example, you can write a Visual Basic.NET to re-add for the Visual C # Windows Forms coloring, or for Visual Basic Class to add comments. To provide this functionality, Visual Basic.NET extension is no long

43、er using the old model, you need to change the expansion of the application object to use the advantages of new features. Many applications are classified as a "tool" type of procedure. Used to manipulate files, registry settings tools like the application does not require any additional m

44、odifications often can be upgraded. After the upgrade, there are many new features available, such as the language of the exception handling to catch file system errors, and use. NET Framework class registry registry manipulation. It should be noted that, dependent on the particular Visual Basic 6.0

45、 application performance characteristics (such as arcade games) may require some modification, because Visual Basic.NET have different performance characteristics. Visual Basic.NET in the game for support, you can use Microsoft DirectX ® 7 or a new version of the GDI. GDI + introduces many new

46、features, including all two-dimensional pixel, the image fidelity of the Alpha and graphics file formats supported by combination of extended support. Data Visual Basic 6.0 provides the following types of data access types:· ActiveX Data Objects (ADO) * Remote Data Objects (RDO) * Data Access O

47、bject (DAO) Visual Basic.NET introduces an enhanced version of ADO, called ADO.NET. ADO.NET disconnected data used, and distributed applications to improve performance in ADO. ADO.NET for the Windows Forms control providing read / write data binding for Web Forms data binding to provide read-only. I

48、n DAO, RDO, and ADO minor changes (in the language section of this document described), it can still be used in Visual Basic.NET code. However, Visual Basic.NET does not support DAO and RDO data binding to controls, data controls, or "RDO user" link. If your application contains the DAO or

49、 RDO data binding, we recommend that you leave them in Visual Basic 6.0, or in the works before the upgrade to Visual Basic.NET, DAO and RDO data binding first upgrade to the ADO, ADO support for Windows Forms data binding. On how to do this work of information, can help to get Visual Basic 6.0. In

50、summary, we recommend that you use Visual Basic 6.0 project ADO. Upgrade Upgrade code, Visual Basic.NET to create a new project has been upgraded, and you do most of the necessary language and object changes. The following section provides a few examples of code upgrades. Variant to object Visual Ba

51、sic, Variant data type support for an earlier version, you can assign it to any basic types (other than fixed-length strings), Empty, Error, Nothing, and Null. In Visual Basic.NET in, Variant and Object data types into a new data type: Object. Object can be assigned to the basic data types, Empty, N

52、othing, Null, and object. When you upgrade to Visual Basic.NET project, all the variables are declared as Variant turned into Object. Similarly, when the code is inserted after the editor, Variant keyword is replaced with Object Visual Basic Forms to Windows Forms Visual Basic.NET has a new form pac

53、kage (ie, Windows Forms), which provides access to local support and a place menu editor. Your existing Visual Basic form will be upgraded to Windows Forms InterfaceEarlier versions of Visual Basic, public classes are often hidden from the user interface. In Visual Basic.NET, you can "code edit

54、or" in the view and edit them. When the project is upgraded, you can choose whether to automatically create interfaces for the public class statement. Upgrade report and comments After the upgrade project will add to your project update report outlining the need for the code has been upgraded a

55、ll the changes. In addition, the code will also add comments to remind you to potential problems. These comments are automatically displayed in the Visual Studio.NET "task list". Programming recommendations This section provides suggestions about writing code in order to minimize the work

56、required to upgrade to Visual Basic.NET changes. Use early binding Visual Basic 6.0 and Visual Basic.NET support the late binding objects, that is, declare a variable as the Object data type, and at run time to allocate it to class. However, during the upgrade, the default property in the resolution

57、, or in the underlying object model has changed, properties, methods, and events need to convert the case, the late-bound object problems. For example, suppose you have a form called "Form1", a label called "Label1". In Visual Basic.NET Windows Form, the labeling of the Caption p

58、roperty is called Text. When your code is upgraded, Caption property of all instances into a Text, but because there is no late-bound object type, Visual Basic can not detect the type of object, or do not know whether the need to convert all the properties. In these cases, you need to change the cod

59、e after the upgrade themselves When your Visual Basic 6.0 code to use Object and Variant variables, if you want to specify variables, perform operations on the variables or variables passed to the function, we recommend that you use explicit conversion Visual Basic.NET support function overloading based on parameter type. Visual Basic.NET the type of call based on parameters which function. If you pass the integer to Environ (), then call the integer version. If you pass a string, then the call string version. Variant or Object data type will be passed to the overloaded func