英语翻译1.4 ActiveX EXEs and Visual Basic 2005Neither creating n

英语翻译
1.4 ActiveX EXEs and Visual Basic 2005
Neither creating nor consuming ActiveX EXEs is explicitly supported in Visual Basic 2005.The .NET platform underlying Visual Basic 2005 provides better mechanisms for achieving the same result:
· Remote execution.WebServices and .NET remoting provide a more robust,secure and thorough mechanism for executing code on remote computers.
· Multi-threading.Visual Basic 2005 has first-class support for creating multithreaded applications with fine-grained control over thread creation,destruction and prioritization,as well as mutexes and semaphores.
· DLLs and executables.Although Visual Basic 2005 does not support executables that double as class libraries,the product has much better support for different types of executables such as console applications,Windows applications,Windows services,web applications and easily versioned DLLs that are not vulnerable to the "DLL hell" versioning problems common to COM applications.
The Visual Basic 2005 upgrade wizard cannot upgrade a Visual Basic 6 ActiveX EXE.If you try to upgrade an Active EXE project,the upgrade wizard warns that upgrading ActiveX EXEs is not supported,and then exits.
1.5 Moving ActiveX EXEs Forward to Visual Basic 2005
For developers who have a compelling business need to overhaul an ActiveX EXE,standardizing on Visual Basic 2005 is an appropriate strategy which means finding a way to upgrade or rewrite the entire ActiveX EXE to Visual Basic 2005.
1.5.1 Upgrading the ActiveX EXE code
Some or most of the business logic in a Visual Basic 6 ActiveX EXE can usually be automatically upgraded to Visual Basic 2005,with some rework required after the upgrade wizard is finished.
Although the Visual Basic 2005 upgrade wizard does not support upgrading Visual Basic 6 ActiveX EXEs,with a little trickery,the Visual Basic 2005 upgrade wizard can be fooled into performing the upgrade.
To upgrade an ActiveX EXE project,change the project type from "ActiveX EXE" to "ActiveX DLL" in the Visual Basic 6 project properties.After doing this,the upgrade wizard recognizes the project as a code library rather than an ActiveX EXE.The resulting Visual Basic 2005 project will be a DLL rather than an executable.