INFO: What Is New for eMbedded Visual Basic Developers? (260089)

MORE INFORMATION

1. eMbedded Visual Basic 3.0 lives in its own design environment. Designed specifically for creating applications to run on embedded devices, Microsoft eMbedded Visual Basic 3.0 offers a new integrated development environment (IDE) that provides a rapid application development tool tailored specifically for the Windows CE platform.
   
   
   • Limited to real Windows CE functionality and controls:
     
     In the past, developing Visual Basic applications for Windows CE platforms required the desktop version of the development software, along with a plug-in software development kit (SDK). Now, however, such development is simplified. Microsoft eMbedded Visual Basic 3.0 is a stand-alone IDE incorporating only the controls, properties, and functionality that is applicable to Windows CE platforms. Developers no longer need to worry whether or not a control in the toolbox is supported for their target platform because eVB only lists compatible controls and libraries in the component/reference dialog box.
   • Integrated debugger:
     
     Microsoft eMbedded Visual Basic 3.0 includes a debugger that is integrated into the IDE and provides assistance in finding run-time bugs in code. This allows you to set breakpoints directly in the IDE. It supports setting breakpoints, defining watch expressions, and stepping through code one statement at a time. However, Windows CE-based eMbedded Visual Basic application cannot directly communicate with the debugging environment by means of the Stop command or the Debug object. All debugging actions must be initiated from the debugger IDE.
   • Project Properties dialog box:
     
     The Project Properties dialog box does not automatically display when creating a new eVB project. You can display the Project Properties dialog box by clinking to select Project Properties on the Project menu.
     
     Project properties has a new attribute - Component to update. The developer can select one of the two options to download that type of component each time the application is run on the target device. The two options are Runtime file and Project components.
   • File extensions:
     
     The file extensions of eMbedded Visual Basic projects have been changed. Applications that are created in eMbedded Visual Basic 3.0 have file extensions of *.ebp, rather than *.vbp. Form modules have file extension of *.ebf, rather than *.frm.
   • New Remote Tools:
     
     File Viewer is similar to the desktop Windows Explorer. Configure Platform Manager manages connections to Windows CE devices and emulators.
2. Ability to target Pocket PC devices.
   • Updated for Pocket PC UI:
     
     Not only are the controls tailored to the target platform, the IDE also provides a customized set of menus, tools, and toolbars to enhance developer productivity in creating applications for Windows CE platforms, such as the Pocket PC.
   • MenuBar control:
     
     The MenuBar control is placed on a Form to provide an application menu for a Pocket PC application. The control supports both buttons and standard menus. It can be added to the toolbox through the Components dialog box, just like any ActiveX control. The online Help documents provide sample code that illustrates how to instantiate a MenuBar control and provide functionality for the various menu items. The Blackjack sample included with the Pocket PC SDK illustrates how to use the new control.
   • CommandBar control:
     
     The Microsoft CE CommandBar 3.0 control is not supported in the Pocket PC platform. This can be seen by its absence in the Project and Component dialog box. However, an attempt to add the control to the form does not pose any error until you run the project on the emulation or the device.
   • Soft input panel (SIP) interaction and events:
     
     When you require your application to accept user input that cannot be handled with command buttons, check boxes, or other interface controls, you now have the option to use the soft input panel (SIP). The SIP is the primary means of entering customized data for the user.
3. Ability to target Handheld PC 2000 devices.
   • Upgraded Pocket Internet Support:
     
     The browser has been upgraded to the equivalent of Internet Explorer (IE) version 4.0 on the desktop. This includes support for HTML 4.0, XML/XSL, DHTML, and animated GIFs.
   • New APIs support:
     
     A number of new APIs are available for developers including the Crypto API (CAPI) for adding additional encryption software, Microsoft Message Queue (MSMQ) for exactly-once in-order message delivery providing reliable transactions while disconnected, and the SmartCard API enabling SmartCard applications.
4. Menu Editor Removed. The Menu Editor has been removed from the IDE. Projects created in previous versions that contain a Menu from the Menu Editor have the Menu removed when opened in the new IDE. Either the CommandBar control (for H/PC Pro and Palm-Size PC 1.2) or the MenuBar control (Pocket PC) have to be used instead.
   
   
5. New F1 Functionality. The code window supports new F1 Help functionality. To get help for a particular property or keyword when in the code window, position the cursor in the word you want information about, and then press the F1 key to bring up Windows CE Help. The system searches for the word in the Help index, and opens the appropriate page. In the event that there is more than one match for your request, a dialog box that lists the available topics opens.
   
   
6. ADOCE version 3.0 control. The Microsoft ActiveX Data Objects for Windows CE (ADOCE) version 3.0 control is an extended version of the previous ADOCE control. This new version of the control features support of the Connection object, and allows the developer to specify a connection to an OLE DB Provider or to the proprietary Windows CE database (CEDB).