版權(quán)說(shuō)明:本文檔由用戶提供并上傳,收益歸屬內(nèi)容提供方,若內(nèi)容存在侵權(quán),請(qǐng)進(jìn)行舉報(bào)或認(rèn)領(lǐng)
文檔簡(jiǎn)介
1、<p><b> 中文5230字</b></p><p><b> 外文文獻(xiàn)原文:</b></p><p> Ready to upgrade Visual Basic 6.0 applications to Visual Basic.NET </p><p><b> Outline<
2、/b></p><p> This document is to use Microsoft ® Visual Basic ® developers to provide the application to </p><p> upgrade to Microsoft Visual Basic.NET recommendations. </p>
3、<p> Visual Basic.NET can open the Visual Basic 6.0 projects to Visual 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 pro
4、ject. The purpose of this document is on the design and implementation of the current Visual Basic project to provide recommendations to upgrade to Visual Basic.NET only after a minimum of changes. Where appropriate, we
5、will use the new language structure; However, this document is not a lan</p><p> Visual Basic.NET is the next version of Visual Basic. Microsoft re-designed the product, rather than simply as Visual Basic 6
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 Form
7、s and Web Forms); used to access the disconnected ADO data source for the new version; the latest model of the language, remove the traditional keyword, im</p><p> These new features for the Visual Basic de
8、veloper opened a new door: Use the Web Forms and ADO.NET, to rapidly develop scalable Web sites; through the inheritance, the language can be a real object-oriented programming support; Windows window body itself to supp
9、ort access and visual inheritance; now deploy your application as the executable files and components from one directory to another directory so simple. </p><p> Visual Basic.NET is now available in other l
10、anguages 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 writ
11、ten in different languages. Using the 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
12、. NET Framework </p><p> Why not 100 percent compatible with Visual Basic.NET? </p><p> Visual Basic.NET can be designed to consider two options: Update to the existing code base. NET framewor
13、k 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 the platform for full and unrestricted acce
14、ss, and to ensure the next generation of Visual Basic can access Web application, the right decision in the new platform the generation from scratch. </p><p> For example, in Windows Forms in a number of ne
15、w features can be used as new controls or more properties to 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 Win
16、dows form. </p><p> Our main goals is to ensure that the Visual Basic code can be completely and use of other languages (such as Microsoft Visual C # ?, or Microsoft Visual C + + ®) write code to work,
17、 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 lang
18、uage, Visual Basic now has the same variable type, array, user-defined types, classes and interface</p><p> Visual Basic is now a true object-oriented language; some non-intuitive and inconsistent feature h
19、as been removed from the language, such as GoSub / Return and DefInt. </p><p> The result is a Visual Basic more dynamic, it will continue to be Windows-based application that creates the best tools, and no
20、w to create the next generation of Web site to be the best tool. </p><p> Upgrade to Visual Basic.NET </p><p> Visual Basic.NET from the basic principles of the traditional Windows development
21、 to build next generation Web and n-tier applications. Therefore, you need to upgrade the code to use the advantages of Visual Basic.NET. </p><p> Open in Visual Basic.NET in Visual Basic 6.0 project, it wi
22、ll automatically appear, "Upgrade 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
23、 Visual Basic 6.0 can not open a new Visual Basic.NET project. </p><p> Works after the upgrade, language change due to syntax changes, your form is converted to Visual Basic 6.0 Windows Forms. In most case
24、s, 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
25、oo. After the upgrade, may also need to change your applications to use Visual Basic.NET some of the new features. </p><p> At the same time using Visual Basic 6.0 and Visual Basic.NET </p><p>
26、 Visual Basic.NET support for Visual Basic 6.0 upgrade project; If you have a Visual Basic, version 1 to version 5, the preparation of the project, we recommend that you load it into VB6 (the choice to upgrade Microsoft
27、 ActiveX ® controls), compile and save the project, and then upgrade the project to Visual Basic.NET. </p><p> Visual Basic.NET and Visual Basic 6.0 can be installed on the same computer and run. Simil
28、arly, with 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
29、COM components written in other languages to work together. For example, can be written using Visual Basic 6.0 ActiveX controls to Visual Basic.NET Windows Forms drag and drop, use Visual Ba</p><p> Compone
30、nts with Visual Basic.NET compiler and compiled using Visual Basic 6.0 runtime components are slightly different. For the initial application, as Visual Basic.NET objects through garbage collection release, so if the obj
31、ect is explicitly removed from memory before they actually delete, may be a delay. Other differences, such as variant / object changes will note later in this article. A result of these differences is a common applicatio
32、n with Visual Basic.NET Visual Basic 6.0 application </p><p> In addition, Visual Basic.NET to Visual Basic.NET and Visual Basic 6.0 components in between these components do not binary compatible. Componen
33、ts 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
34、to replace the old files as easy. You have to do is to ensure that classes and methods compatible with earlier versions. </p><p> Architecture proposed</p><p> . NET platform on the improvemen
35、t 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 file transfer and deployment (no longer is a
36、 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. </p><p> Browser-based applic
37、ations </p><p> Visual Basic 6.0 and Microsoft Visual Studio ® 6.0 to create a browser-based Internet and Intranet applications provide the following types of technologies:</p><p> ·
38、 Webclass</p><p> · DHTML project</p><p> · ActiveX Document</p><p> · Active Server Pages (ASP) </p><p> Visual Basic.NET introduces an enhanced ver
39、sion that is ASP ASP.NET, and with the Web form to the architecture, Web form is the case with Visual Basic HTML page. Architecture is based on the server.</p><p> The following recommendations and a list o
40、f 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 projects:</p><p> Recommend that you follow Micro
41、soft 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 A
42、SP, you can use ASP, ASP.NET and Web Forms 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. </p&
43、gt;<p> DHTML applications, including DHTML page and the client DLL. These applications are not automatically upgraded to Visual Basic.NET. We recommend that you leave these applications in the Visual Basic 6.0.
44、</p><p> 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, o
45、r possible, to replace the ActiveX user control documents. </p><p> Visual Basic 6.0 ActiveX documents and DHTML applications with Visual Basic.NET technology work together. For example, you can navigate fr
46、om a Visual Basic.NET Web Forms to Visual Basic 6.0 DHTML page, and vice versa. </p><p> Visual Basic.NET is no longer a Webclass. Webclass application will be upgraded to ASP.NET, but after the upgrade you
47、 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 A
48、SP's Windows DNA platform. </p><p> Client / server project </p><p> Visual Basic 6.0 to provide for creating client / server application of the following technologies:</p><p>
49、; · Visual Basic form</p><p> · Microsoft Transaction Server (MTS) / COM + middle tier objects </p><p> * User Control </p><p> Visual Basic.NET has a new form package
50、, or Windows 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. </p><p> Visual
51、 Basic.NET development to improve the middle layer of MTS and COM + Component Services components support. Using the unified debugger, you can access from the client application MTS / COM + components, and then returned
52、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 debugging information and n
53、o optimization). </p><p> 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 requ
54、est method. They use industry-standard XML data transfer and return, allowing access to their other language and platform features. Although they do not support the MTS transaction, but when you do not need distributed t
55、ransactions, but still need to work with other platforms, you can put MTS / COM + components into We</p><p> Works upgrade, upgrade to Windows controls user controls; but the custom attribute tags to set up
56、 and assign shortcut keys will not upgrade. </p><p> Single application </p><p> Visual Basic 6.0 supports the following types of single-generation applications: </p><p> * Singl
57、e-database application</p><p> · Visual Basic add-ins </p><p> * Tools programs and games </p><p> Single database application, some Visual Basic applications, which is char
58、acterized in the Microsoft Access database to store data. These applications when upgrading to Visual Basic.NET certain restrictions (see later in this document, "data" section). </p><p> Visual B
59、asic.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 can in any language in V
60、isual 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 t
61、his functionality, Visual Basic.NET extension is no </p><p> Many applications are classified as a "tool" type of procedure. Used to manipulate files, registry settings tools like the application
62、does not require any additional modifications 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 Fram
63、ework class registry registry manipulation. It should be noted that, dependent on the particular Visual Basic 6.0 application performance charact</p><p><b> Data </b></p><p> Visua
64、l Basic 6.0 provides the following types of data access types:</p><p> · ActiveX Data Objects (ADO) </p><p> * Remote Data Objects (RDO) </p><p> * Data Access Object (DAO)
65、</p><p> 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 con
66、trol providing read / write data binding for Web Forms data binding to provide read-only. </p><p> In DAO, RDO, and ADO minor changes (in the language section of this document described), it can still be us
67、ed 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 RDO data binding, we reco
68、mmend 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</p><p> In summary, we
69、 recommend that you use Visual Basic 6.0 project ADO. </p><p><b> Upgrade </b></p><p> Upgrade code, Visual Basic.NET to create a new project has been upgraded, and you do most of
70、the necessary language and object changes. The following section provides a few examples of code upgrades. </p><p> Variant to object </p><p> Visual Basic, Variant data type support for an ea
71、rlier 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 as
72、signed to the basic data types, Empty, Nothing, Null, and object. </p><p> When you upgrade to Visual Basic.NET project, all the variables are declared as Variant turned into Object. Similarly, when the cod
73、e is inserted after the editor, Variant keyword is replaced with Object </p><p> Visual Basic Forms to Windows Forms </p><p> Visual Basic.NET has a new form package (ie, Windows Forms), which
74、 provides access to local support and a place menu editor. Your existing Visual Basic form will be upgraded to Windows Forms </p><p><b> Interface</b></p><p> Earlier versions of V
75、isual Basic, public classes are often hidden from the user interface. In Visual Basic.NET, you can "code editor" in the view and edit them. When the project is upgraded, you can choose whether to automatically
76、create interfaces for the public class statement. </p><p> Upgrade report and comments </p><p> After the upgrade project will add to your project update report outlining the need for the code
77、 has been upgraded all 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". </p>
78、<p> Programming recommendations </p><p> This section provides suggestions about writing code in order to minimize the work required to upgrade to Visual Basic.NET changes. </p><p> Us
79、e early binding </p><p> 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
80、 the upgrade, the default property in the resolution, 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
81、 a form called "Form1", a label called "Label1". </p><p> In Visual Basic.NET Windows Form, the labeling of the Caption property is called Text. When your code is upgraded, Caption prope
82、rty 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
83、 change the code after the upgrade themselves </p><p> 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
84、 passed to the function, we recommend that you use explicit conversion </p><p> Visual Basic.NET support function overloading based on parameter type. Visual Basic.NET the type of call based on parameters w
85、hich 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 function, the code may
86、 cause compile error or run-time error. If you use the following example shows an explicit conversion, then upgrade to Visual Basic.NET code after work. </p><p> Late-bound object using explicit conversion
87、is good coding practice. It makes code easier to judge intent, so you can easily transfer project in Visual Basic.NET.</p><p> Date date using stored </p><p> Early versions of Visual Basic Do
88、uble data types support the use of storage and manipulation of dates. In Visual Basic.NET can not do so, because the date is not stored in the internal double-precision type.</p><p> . NET Framework provide
89、s ToOADate and FromOADate function for the double precision type and date of conversion between the types. However, when you upgrade to Visual Basic.NET project after the storage period using the double-precision type of
90、 code is difficult to judge the intent. To avoid your Visual Basic.NET code for unnecessary changes, always use the Date data type stores date </p><p> Default properties without parameters analysis </p&
91、gt;<p> In Visual Basic 6.0, many objects are open default property, as a programming shortcut, you can omit the default property. </p><p> In the late binding example, the default properties are re
92、solved at run time, MsgBox TextBox default value of the property will be displayed as Text1. </p><p> No parameters Visual Basic.NET does not support default properties, which does not allow this programmin
93、g shortcut. When you upgrade project, Visual Basic.NET resolve default property without parameters, but rely on run-time analysis of late binding with the law can not automatically resolve. In these cases, you must chang
94、e your code. Another complex issue is that many libraries use the property called _Default to achieve the default property. _Default Property as an agent, calls are delivered t</p><p><b> 中文翻譯稿</b&
95、gt;</p><p> 準(zhǔn)備將 Visual Basic 6.0 應(yīng)用程序升級(jí)到 Visual Basic.NET</p><p><b> 概述 </b></p><p> 本文檔為使用 Microsoft® Visual Basic® 的開(kāi)發(fā)人員提供有關(guān)將應(yīng)用程序升級(jí)到 Microsoft Visual
96、 Basic.NET 的建議。</p><p> Visual Basic.NET 可以打開(kāi) Visual Basic 6.0 工程并將其升級(jí)到 Visual Basic.NET 技術(shù)。但在大多數(shù)情況下,將工程升級(jí)到 Visual Basic.NET 后,需要對(duì)工程進(jìn)行一些修改。本文檔的目的是就設(shè)計(jì)和實(shí)現(xiàn)當(dāng)前 Visual Basic 工程提供建議,以便升級(jí)到 Visual Basic.NET 后只需進(jìn)行最少的
97、修改。在適當(dāng)?shù)牡胤?,我們將使用新的語(yǔ)言構(gòu)造;但是,本文檔并不用作 Visual Basic.NET 的語(yǔ)言參考。</p><p> 什么是 Visual Basic.NET?</p><p> Visual Basic.NET 是 Visual Basic 的下一個(gè)版本。Microsoft 重新設(shè)計(jì)了產(chǎn)品,而不僅僅是簡(jiǎn)單地為 Visual Basic 6.0 添加某些新功能。新版本比以
98、前的版本更易于編寫分布式應(yīng)用程序,如 Web 和企業(yè) n-層系統(tǒng)。Visual Basic.NET 具有兩個(gè)新的窗體包(Windows 窗體和 Web 窗體);用于訪問(wèn)斷開(kāi)連接的數(shù)據(jù)源的 ADO 新版本;最新型的語(yǔ)言、刪除了傳統(tǒng)關(guān)鍵字、提高了類型安全性并公開(kāi)了高級(jí)開(kāi)發(fā)人員需要的低級(jí)別構(gòu)造。</p><p> 這些新功能為 Visual Basic 開(kāi)發(fā)人員開(kāi)啟了一扇新的大門:使用 Web 窗體和 ADO.NET
99、,可以快速開(kāi)發(fā)可伸縮的 Web 站點(diǎn);通過(guò)繼承,該語(yǔ)言可真正支持面向?qū)ο蟮木幊?;Windows 窗體本身支持訪問(wèn)和可視繼承;現(xiàn)在部署您的應(yīng)用程序就像把可執(zhí)行文件和組件從一個(gè)目錄復(fù)制到另一個(gè)目錄那么簡(jiǎn)單。</p><p> Visual Basic.NET 現(xiàn)在可與其他 Microsoft Visual Studio.NET 語(yǔ)言完全集成。您不僅可以用不同的編程語(yǔ)言開(kāi)發(fā)應(yīng)用程序組件,而且您的類現(xiàn)在可以通過(guò)跨語(yǔ)言繼
溫馨提示
- 1. 本站所有資源如無(wú)特殊說(shuō)明,都需要本地電腦安裝OFFICE2007和PDF閱讀器。圖紙軟件為CAD,CAXA,PROE,UG,SolidWorks等.壓縮文件請(qǐng)下載最新的WinRAR軟件解壓。
- 2. 本站的文檔不包含任何第三方提供的附件圖紙等,如果需要附件,請(qǐng)聯(lián)系上傳者。文件的所有權(quán)益歸上傳用戶所有。
- 3. 本站RAR壓縮包中若帶圖紙,網(wǎng)頁(yè)內(nèi)容里面會(huì)有圖紙預(yù)覽,若沒(méi)有圖紙預(yù)覽就沒(méi)有圖紙。
- 4. 未經(jīng)權(quán)益所有人同意不得將文件中的內(nèi)容挪作商業(yè)或盈利用途。
- 5. 眾賞文庫(kù)僅提供信息存儲(chǔ)空間,僅對(duì)用戶上傳內(nèi)容的表現(xiàn)方式做保護(hù)處理,對(duì)用戶上傳分享的文檔內(nèi)容本身不做任何修改或編輯,并不能對(duì)任何下載內(nèi)容負(fù)責(zé)。
- 6. 下載文件中如有侵權(quán)或不適當(dāng)內(nèi)容,請(qǐng)與我們聯(lián)系,我們立即糾正。
- 7. 本站不保證下載資源的準(zhǔn)確性、安全性和完整性, 同時(shí)也不承擔(dān)用戶因使用這些下載資源對(duì)自己和他人造成任何形式的傷害或損失。
最新文檔
- visual basic.net編寫南方全站儀實(shí)時(shí)通訊程序
- 外文翻譯---visual basic編程語(yǔ)言
- 外文翻譯----visual basic編程語(yǔ)言
- visual basic程序設(shè)計(jì)
- visual basic畢業(yè)設(shè)計(jì)外文翻譯
- 外文翻譯---visual basic 語(yǔ)言與算法
- 外文翻譯---visual basic 語(yǔ)言與算法
- visual basic 程序設(shè)計(jì)教程
- visual basic程序設(shè)計(jì) (2)
- 外文翻譯--Visual Basic編程語(yǔ)言概述.doc
- vb外文翻譯--- visual basic語(yǔ)言和算術(shù)
- 外文翻譯--Visual Basic編程語(yǔ)言概述.doc
- 外文翻譯--Visual Basic編程語(yǔ)言概述.doc
- 外文翻譯--Visual Basic編程語(yǔ)言概述.doc
- 《visual basic程序設(shè)計(jì)》大作業(yè)-
- 《visual basic程序設(shè)計(jì)》補(bǔ)修試題
- 計(jì)算機(jī)外文資料翻譯---visual basic簡(jiǎn)介
- 外文翻譯--visual basic數(shù)據(jù)庫(kù)連接介紹指南
- 計(jì)算機(jī)專業(yè)外文翻譯---visual basic 語(yǔ)言與算法
- 淺談利用visual basic環(huán)境開(kāi)發(fā)公路應(yīng)用系統(tǒng)
評(píng)論
0/150
提交評(píng)論