项目管理外文翻译Word文档格式.docx

项目管理外文翻译Word文档格式.docx

《项目管理外文翻译Word文档格式.docx》由会员分享，可在线阅读，更多相关《项目管理外文翻译Word文档格式.docx（14页珍藏版）》请在冰豆网上搜索。

developerstoprovidetheapplicationto

upgradetoMicrosoftVisualBasic.NETrecommendations.

VisualBasic.NETcanopentheVisualBasic6.0projectstoVisualBasic.NETupgradeitstechnology.However,inmostcases,theprojecttoupgradetoVisualBasic.NET,youneedtomakesomechangestotheproject.ThepurposeofthisdocumentisonthedesignandimplementationofthecurrentVisualBasicprojecttoproviderecommendationstoupgradetoVisualBasic.NETonlyafteraminimumofchanges.Whereappropriate,wewillusethenewlanguagestructure;

However,thisdocumentisnotalanguagereferenceforVisualBasic.NET.WhatisVisualBasic.NET?

VisualBasic.NETisthenextversionofVisualBasic.Microsoftre-designedtheproduct,ratherthansimplyasVisualBasic6.0addsomenewfeatures.Thenewversioneasierthanpreviousversionsofthepreparationofdistributedapplications,suchasWebandenterprisen-tiersystem.VisualBasic.NETwithtwonewformspackages（WindowsFormsandWebForms）;

usedtoaccessthedisconnectedADOdatasourceforthenewversion;

thelatestmodelofthelanguage,removethetraditionalkeyword,improvedtypesecurityandadvanceddevelopersneedtoopenalow-levelstructure.

ThesenewfeaturesfortheVisualBasicdeveloperopenedanewdoor:

UsetheWebFormsandADO.NET,torapidlydevelopscalableWebsites;

throughtheinheritance,thelanguagecanbearealobject-orientedprogrammingsupport;

Windowswindowbodyitselftosupportaccessandvisualinheritance;

nowdeployyourapplicationastheexecutablefilesandcomponentsfromonedirectorytoanotherdirectorysosimple.

VisualBasic.NETisnowavailableinotherlanguagesfullyintegratedwithMicrosoftVisualStudio.NET.Youcannotonlyusedifferentprogramminglanguagetodevelopapplicationcomponents,andyourclasscannowcross-languageinheritancetoinheritclasseswrittenindifferentlanguages.Usingtheunifieddebuggercannowdebugmultiplelanguageapplications,regardlessofwhethertheyarerunlocallyoronaremotecomputer.Finally,nomatterwhatlanguageyouuse,Microsoft.NETFrameworkistheMicrosoftWindows®

andInternetprovidesarichAPI.

Whynot100percentcompatiblewithVisualBasic.NET?

VisualBasic.NETcanbedesignedtoconsidertwooptions:

Updatetotheexistingcodebase.NETframeworktorun;

orbuildfromscratchtofullyleveragetheplatform'

sadvantages.Toreachthecustomersmostinneedoffeatures（suchasinheritanceandThreading）,toprovidetheplatformforfullandunrestrictedaccess,andtoensurethenextgenerationofVisualBasiccanaccessWebapplication,therightdecisioninthenewplatformthegenerationfromscratch.

Forexample,inWindowsFormsinanumberofnewfeaturescanbeusedasnewcontrolsormorepropertiestoaddtotheexistingcodebase.However,thiswillputallotherimportantfunctions（suchassecurityandvisualinheritance）thecostofsuccessiontotheWindowsform.

OurmaingoalsistoensurethattheVisualBasiccodecanbecompletelyanduseofotherlanguages（suchasMicrosoftVisualC#™,orMicrosoftVisualC++®

）writecodetowork,andtoVisualBasicdeveloperseasytouse.NETFrameworkfeatureswithoutusingthetraditionalWindowsAPIprogrammingtoolstomakework.AndVisualC++andanyothercommonlanguageruntimetotargetthesamelanguage,VisualBasicnowhasthesamevariabletype,array,user-definedtypes,classesandinterfaces;

butwehaveremovedfromthelanguageofcertainfunctions,Forexample,anarrayoffixed-lengthstringsandnon-zero.

VisualBasicisnowatrueobject-orientedlanguage;

somenon-intuitiveandinconsistentfeaturehasbeenremovedfromthelanguage,suchasGoSub/ReturnandDefInt.

TheresultisaVisualBasicmoredynamic,itwillcontinuetobeWindows-basedapplicationthatcreatesthebesttools,andnowtocreatethenextgenerationofWebsitetobethebesttool.

UpgradetoVisualBasic.NET

VisualBasic.NETfromthebasicprinciplesofthetraditionalWindowsdevelopmenttobuildnextgenerationWebandn-tierapplications.Therefore,youneedtoupgradethecodetousetheadvantagesofVisualBasic.NET.

OpeninVisualBasic.NETinVisualBasic6.0project,itwillautomaticallyappear,"

UpgradeWizard"

toguideyouthroughtheupgradeprocess,andautomaticallycreateanewVisualBasic.NETproject（yourexistingprojectwillnotchange）.Thisisaone-wayprocess;

inVisualBasic6.0cannotopenanewVisualBasic.NETproject.

Worksaftertheupgrade,languagechangeduetosyntaxchanges,yourformisconvertedtoVisualBasic6.0WindowsForms.Inmostcases,theupgradecodealsoneedtobesomechanges.ThisisbecausecertainobjectsandlanguagefeaturesinVisualBasic.NETisnotequivalenttothecontent,orforautomaticupdates,theequivalentcontentdifferencestoo.Aftertheupgrade,mayalsoneedtochangeyourapplicationstouseVisualBasic.NETsomeofthenewfeatures.

AtthesametimeusingVisualBasic6.0andVisualBasic.NET

VisualBasic.NETsupportforVisualBasic6.0upgradeproject;

IfyouhaveaVisualBasic,version1toversion5,thepreparationoftheproject,werecommendthatyouloaditintoVB6（thechoicetoupgradeMicrosoftActiveX®

controls）,compileandsavetheproject,andthenupgradetheprojecttoVisualBasic.NET.

VisualBasic.NETandVisualBasic6.0canbeinstalledonthesamecomputerandrun.Similarly,withVisualBasic.NETandVisualBasic6.0applicationswrittencanalsobeinstalledonthesamecomputerandrunconcurrently.ComponentswrittenusingVisualBasic.NETwithearlierversionsofVisualBasic,andCOMcomponentswritteninotherlanguagestoworktogether.Forexample,canbewrittenusingVisualBasic6.0ActiveXcontrolstoVisualBasic.NETWindowsFormsdraganddrop,useVisualBasic.NETClassLibraryinVisualBasic6.0COMobjects,ortoVisualBasic6.0executabletheVisualBasic.NETLibrary.

ComponentswithVisualBasic.NETcompilerandcompiledusingVisualBasic6.0runtimecomponentsareslightlydifferent.Fortheinitialapplication,asVisualBasic.NETobjectsthroughgarbagecollectionrelease,soiftheobjectisexplicitlyremovedfrommemorybeforetheyactuallydelete,maybeadelay.Otherdifferences,suchasvariant/objectchangeswillnotelaterinthisarticle.AresultofthesedifferencesisacommonapplicationwithVisualBasic.NETVisualBasic6.0applicationrunningwithsimilarcharacteristics,butnotidentical.

Inaddition,VisualBasic.NETtoVisualBasic.NETandVisualBasic6.0componentsinbetweenthesecomponentsdonotbinarycompatible.Componentsarenowmorepowerfulthanbefore,versionmanagementanddeploymentsystem,youcansimplycopyfilestoadirectory（nolongerRegSvr32）todeploythefile,andupgradetonewversionofthecomponentasanewreplacetheoldfilesaseasy.Youhavetodoistoensurethatclassesandmethodscompatiblewithearlierversions.

Architectureproposed

.NETplatformontheimprovementofearlyarchitectureonthescalabilityofdistributedapplicationsandtoprovidemorepowerfulsupport,althoughithasdisconnecteddataaccess,message-basedHTTP-basedanddeployment（nolongerisacomponentregistration）.Totakefulladvantageofthesefeaturesinthedesignofyourapplicationarchitectureused,shouldbeusedinVisualBasic.NETsimilararchitecture.

Browser-basedapplications

VisualBasic6.0andMicrosoftVisualStudio®

6.0tocreateabrowser-basedInternetandIntranetapplicationsprovidethefollowingtypesoftechnologies:

·

Webclass

DHTMLproject

ActiveXDocument

ActiveServerPages（ASP）

VisualBasic.NETintroducesanenhancedversionthatisASPASP.NET,andwiththeWebformtothearchitecture,WebformisthecasewithVisualBasicHTMLpage.Architectureisbasedontheserver.

Thefollowingrecommendationsandalistofthemainarchitectureproposedforthedevelopmentofbrowser-basedVisualBasic6.0applicationstoenablethemtoseamlesslymigratetoVisualBasic.NETprojects:

RecommendthatyoufollowMicrosoftguidelinesformulti-tierarchitecturetocreateyourapplication,usingASPtocreateinterfacesusingVisualBasic6.0orVisualC++6.0COMobjecttocreatebusinesslogic.VisualBasic.NETinfullsupportofASP,youcanuseASP,ASP.NETandWebFormsapplicationstocontinuetoexpand.VisualBasic6.0andVisualC++6.0businessobjectscannotbemodifiedorupgradedtoforVisualStudio.NETorVisualStudio.NET.

DHTMLapplications,includingDHTMLpageandtheclientDLL.TheseapplicationsarenotautomaticallyupgradedtoVisualBasic.NET.WerecommendthatyouleavetheseapplicationsintheVisualBasic6.0.

VisualBasic.NETdoesnotsupportActiveXdocuments,thesameastheDHTMLprojectdoesnotautomaticallyupdate.WerecommendyoutostayintheActiveXdocumentapplicationinVisualBasic6.0,orpossible,toreplacetheActiveXusercontroldocuments.

VisualBasic6.0ActiveXdocumentsandDHTMLapplicationswithVisualBasic.NETtechnologyworktogether.Forexample,youcannavigatefromaVisualBasic.NETWebFormstoVisualBasic6.0DHTMLpage,andviceversa.

VisualBasic.NETisnolongeraWebclass.WebclassapplicationwillbeupgradedtoASP.NET,butaftertheupgradeyouneedtomakesomemodifications.WebclassexistingapplicationswithVisualBasic.NETWebFormsandASPapplicationsworktogether,butfornewprojects,werecommendthatyouusewithVisualBasic6.0businessobjectASP'

sWindowsDNAplatform.

Client/serverproject

VisualBasic6.0toprovideforcreatingclient/serverapplicat