Frequently asked questions (FAQ) about eVB (260081)


The information in this article applies to:

  • Microsoft eMbedded Visual Basic 3.0
This article was previously published under Q260081

SUMMARY

This article answers some of the most frequently asked questions (FAQs) about Microsoft eMbedded Visual Basic (eVB) 3.0 from Microsoft eMbedded Visual Tools (eVT) 3.0.

GeneralADOCEMiscellaneous

MORE INFORMATION

General

  • Q. What is eVB?

    A. The Microsoft eMbedded Visual Basic 3.0 integrated development environment (IDE) is the most productive way for developers to build applications for the next generation of Windows CE-based communication, entertainment, and information-access devices. A comprehensive, rapid application development environment helps developers quickly create, debug, and deploy Windows CE applications for a wide range of devices using well-known Microsoft Visual Basic programming tools and techniques.

    back to the top
  • Q. Where can I obtain a copy?

    A. eVB is included in eVT 3.0. You can download eVT from the following Microsoft Web site:

    http://msdn.microsoft.com/mobility/downloads/

    You can also order a CD-ROM version of eMbedded Visual Tools from the following Web site:

    http://msdn.microsoft.com/embedded/prevver/ce.net/

    back to the top
  • Q. What devices can I target?

    A. eVB 3.0 can target the following Windows CE platforms using the Platform Software Development Kits (SDKs) that Microsoft provides:
    • Microsoft Windows Platform SDK for Pocket PC
    • Windows CE Platform SDK (H/PC 2000)
    • Windows CE Platform SDK (H/PC Pro)
    • Windows CE Platform SDK (Palm-size PC 1.2)
    When you import additional SDKs from OEMs and write for those platforms, you can leverage the experience and knowledge that you gather to any custom OEM platform that is running Windows CE.

    eMbedded Visual Tools 3.0 generates code that is compatible with Windows CE versions 2.11, 2.12, and 3.0.

    back to the top
  • Q. What are the system requirements for eVB?

    A. See the following Microsoft Knowledge Base article for eVB system requirements:

    265776 System requirements for eMbedded Visual Basic 3.0

    back to the top
  • Q. Do I need a copy of Visual Basic 6.0?

    A. Visual Basic 6.0 is not required to use eMbedded Visual Basic 3.0 or eMbedded Visual Tools 3.0. eVT and eVB have their own integrated development environment (IDE).

    back to the top
  • Q. What's new in eVB 3.0?

    A. eMbedded Visual Basic 3.0 is a stand-alone integrated development environment (IDE) that is specifically tailored for developing applications to run on Windows CE platforms and devices. Although no part of Microsoft Visual Studio is required to use eVB, eVB can be installed on the same computer as Visual Studio, including Visual Basic 6.0, without interference.

    The IDE is now especially designed to target Windows CE platforms and devices. eVB 3.0 includes the following features:
    • The toolbox, Property window, Components dialog box, References dialog box, and code completion feature are all filtered based on the platform for which you are developing. Only the tools, controls, and properties that are supported in the chosen SDK are displayed. Also, only Windows CE project templates for which you have installed a Windows CE SDK are available as templates.
    • Microsoft eMbedded Visual Basic 3.0 uses a debugger that is now integrated into the IDE. This allows you to set breakpoints directly in the IDE. There are two ways to run programs from the Run menu:
      • Click Play, or press the F5 key. This method starts the application in the debugger, just as it does in desktop Visual Basic.
      • Click Execute, or press the CTRL+F5 key combination, to start the application without activating the debugger.
    • The Project Properties dialog box does not automatically appear when you create a new project. To generate the Project Properties dialog box, click Project and then Project Properties from the menu.
    • The file extensions of eMbedded Visual Basic projects have changed. When you create applications in eVB 3.0, the file extension is *.ebp rather than *.vbp. For additional information about the new features in eVB, click the following article number to view the article in the Microsoft Knowledge Base:

      260089 What is new for eMbedded Visual Basic developers?

    back to the top
  • Q. Where can I find technical information about eVB 3.0?

    A: Documentation on eVB 4.0 is available from several places. In addition to the eVB online help, refer to the following resources:
    • The Microsoft Knowledge Base contains many articles that address eVB-related topics. To search for eVB-related articles, visit the following Microsoft Web site.

      http://support.microsoft.com/default.aspx?pr=wincevb

    • The eVB Release Notes contain information on known issues. You can find many commonly asked questions about specific behavior in this document. In addition to the Readme.txt file that is installed with eVB, the release notes are available in the following Microsoft Knowledge Base article:

      260080 eMbedded Visual Basic 3.0 release notes

    • The MSDN Online Library includes several areas that contain technical articles, presentations, downloads, and online special interest groups that relate to eVB. For more information, visit the following Microsoft Web sites:

      http://msdn.microsoft.com/library/en-us/dnanchor/html/windowsce.asp

      http://msdn.microsoft.com/embedded/windowsce/default.aspx

      http://www.microsoft.com/mobile/pocketpc/default.asp

    • Scott Lewis' VBCE.COM Web site at http://vbce.com is also a very good source for information. Scott also has set up a mailing list for peer-to-peer support, which is available from this site.

      Note VBCE.COM is not affiliated with Microsoft other than the fact that it refers to a Microsoft product.
    • The deVBuzz.com Web site at http://www.devbuzz.com also contains helpful information and technical articles.

      Note deVBuzz.com is not affiliated with Microsoft other than the fact that it refers to a Microsoft product.
    • Although it is written for the first version of VBCE, Larry Roof's Visual Basic Windows CE Programming from Wrox Press is still a great resource.
    back to the top

ADOCE

  • Q. Does eVB 3.0 provide database programmability?

    A. eVB provides database programmability through the ActiveX Data Objects (ADO) control for the Microsoft Windows CE operating system (ADOCE), which provides a subset of ADO for the Windows CE platform. You can download the latest version of ADOCE 3.1 from the following Microsoft Download Center location:

    http://www.microsoft.com/downloads/release.asp?ReleaseID=25437

    Here are some important notes regarding the three current versions of ADOCE:
    • ADOCE 2.0 only works on a Handheld PC (H/PC) 2.0 device that is running Windows CE 2.0.
    • ADOCE 2.0 does not support automatic Database Table Synchronization between the database tables on the desktop and the device.
    • ADOCE 2.1 only works on H/PC Pro 3.0 devices that are running Windows CE 2.11, Palm-size PC 1.2 devices that are running Windows CE 2.11 and with the Palm-size PC 1.2 SDK installed, and the H/PC devices with ROM upgrades (that is, running Windows CE 2.11).
    • ADOCE 2.1 supports automatic Database Table Synchronization.
    • ADOCE is supported on the following Windows CE platforms:
      • Handheld PC Professional Edition 3.0 devices
      • Palm-size PC 1.2 devices
      • Pocket PC 3.0 devices
      • Custom Windows CE platforms created with Microsoft Windows CE Platform Builder
    back to the top
  • Q. Will ADOCE work with eVB?

    A. The ADOCE 3.0 release is currently available with eMbedded Visual Studio version 3.0 and Software Development Kits (SDKs) that released after January 2000. See the documentation that shipped with eMbedded Visual Studio 3.0 or an SDK for further information.

    back to the top
  • Q. What platforms support ADOCE?

    A. ADOCE is supported on multiple Windows CE platforms. To write an application for a specific platform, you must install the Microsoft Platform SDK for that platform and make sure that the SDK is compatible with the development environment you are using. ADOCE is supported on the following Windows CE platforms:
    • Palm-size PC 1.2 Devices ADOCE is supported on this platform by downloading the Palm-size PC Software Development Kit (SDK) from the Microsoft Windows CE Web site. The ADOCE version 2.0 control is included in this SDK.

    • Handheld PC Professional (H/PC Pro) 3.0 Devices ADOCE is supported on this platform by downloading the ADOCE 3.0 SDK from the Microsoft Windows CE Web site. Synchronization is not supported on this platform due to a limitation in the operating system.

    • Handheld PC (H/PC) 2.0 Devices ADOCE is supported on this platform by downloading the ADOCE 3.0 SDK from the Microsoft Windows CE Web site. Synchronization is not supported on this platform due to a limitation in the operating system.

    • Additional Platforms ADOCE is supported on custom Windows CE platforms that you create with Microsoft Windows CE Platform Builder. You must specify support for ADOCE or Visual Basic for Windows CE when you build the platform. For applications to be written on a custom platform, you must use Platform Builder to create a custom SDK for that platform. For more information about custom Windows CE platforms and Platform Builder, search the Microsoft Windows CE Web site for Platform Builder.
    back to the top
  • Q. Where can I find technical information about ADOCE?

    A. Documentation on ADOCE is available from several places. In addition to the eVB online help, see the following resources: back to the top
  • Q. Does ADOCE work in the emulation environment?

    A. ADOCE does work in the emulation environment. You must ensure that you install the emulation components as a part of the ADOCE SDK installation from the eVB CD-ROM. You must also ensure that you copy your database tables to the emulation environment with the EmpFile utility. For additional information about the EmpFile utility, click the following article number to view the article in the Microsoft Knowledge Base:

    212884 How to use the EmpFile utility

    back to the top

Miscellaneous

  • Q. Can I develop eVB 3.0 applications for Palm-size PCs?

    A. Palm-size PCs can be targeted with eVB 3.0. The target Palm-size PCs must be running Windows CE version 2.11 or later. Note that Palm-size PC devices that are running Windows CE version 2.0 or earlier do not include sufficient Component Object Model (COM) support for Windows CE Toolkit for Visual Basic (VBCE) applications.

    To target Palm-size PCs, the associated Windows CE Palm-size PC Platform SDK is required. You can download the Palm-size PC 1.2 SDK from the following Microsoft Download Center location:

    http://www.microsoft.com/downloads/details.aspx?familyid=A403883E-E10A-4C19-BC82-CD1797B5ACD2

    back to the top
  • Q. What tools should I use if I need to write applications for earlier devices, such as a Handheld PC running Windows CE 2.0 or a Palm-size PC running Windows CE 2.01?

    A. Developers who are targeting earlier devices should continue to use the Windows CE Toolkits for Visual Basic and Visual Basic 6.0 in conjunction with Visual Studio.

    back to the top
  • Q. Are ActiveX controls supported in eVB 3.0? Where can I get them?

    A. Yes. ActiveX is supported in Windows CE, and you can use ActiveX controls in your eVB applications. However, you cannot use eVB to develop ActiveX controls. You must use the Windows CE Toolkit for Visual C++ (eVC) for ActiveX control development. In addition, there are a growing number of third-party companies that are either developing or researching the development of ActiveX controls for use in eVB. For the most current information, visit the following Microsoft Web site:

    http://www.microsoft.com/windows/embedded/default.asp

    back to the top
  • Q. Are the same Visual Basic controls supported in eVB 3.0?

    A. Most Visual Basic intrinsic controls (such as CheckBox, TextBox, and CommandButton controls) are supported in eVB. However, there are some differences in control appearance and behavior that correspond to differences in the Windows CE user interface model. There are also differences in the Visual Basic built-in functions that correspond to differences in operating system features. In general, you will find that creating eVB applications is very similar to creating Visual Basic applications on Microsoft Windows 95, Microsoft Windows 98, Microsoft Windows NT, or Microsoft Windows 2000. For more information, see question 7 to follow.

    back to the top
  • Q. Can I use Windows 95, Windows 98, or Windows Me to develop eVB 3.0 applications?

    A. eVB 3.0 supports the following desktop operating systems:
    • Windows 98 Second Edition (US English, German, Japanese)
    • Windows NT 4.0 Service Pack 5 (US English, German, Japanese)
    • Windows 2000 (US English, German, Japanese).

    Note You cannot use the eVB emulator on these operating systems.

    back to the top
  • Q. Can existing Visual Basic applications be ported to eVB 3.0?

    A. You cannot directly port an existing Visual Basic application into eVB due to some limitations and unsupported features in eVB. The amount of work that is required to "port" an existing Visual Basic desktop application to eVB depends on many factors, including the complexity of the application and whether it uses features that are not supported in eVB. It may be significantly easier to create an eVB application from scratch than to port an existing Visual Basic application. For additional information, click the following article numbers to view the articles in the Microsoft Knowledge Base:

    186266 What is handled differently in Windows CE, VBCE, and eVB

    184650 What language features does VB have that VBCE and eVB do not

    189478 What do eVB/VBCE have that Visual Basic doesn't have?

    192459 VBCE unsupported controls, properties, methods, and events

    back to the top
  • Q. How do I debug eVB 3.0 applications?

    A. There are two ways to debug an eVB 3.0 application:
    • Use the emulation environment to debug your application on your Windows NT/2000 development workstation.
    • Use the integrated debugger that is included with eMbedded Visual Basic 3.0. This debugger is integrated into the IDE and helps find run-time bugs in code. This allows you to set breakpoints directly in the IDE. This debugger supports setting breakpoints, defining watch expressions, and stepping through code one statement at a time. However, a Windows CE-based eVB application cannot directly communicate with the debugging environment by means of the Stop command or the Debug object. You must initiate all debugging actions from the debugger IDE.
    back to the top
  • Q. How do I distribute my eVB 3.0 application?

    A. To distribute eVB applications, use the Application Install Wizard that is included with eVB. For additional information about how to distribute eVB applications, click the following article number to view the article in the Microsoft Knowledge Base:

    268309 How to associate an icon with an eVB application

    194837 How to distribute a Visual Basic Windows CE application

    back to the top
  • Q. Can I access Pocket Outlook features (such as contacts and tasks) from eVB 3.0?

    A. If you are using the new Pocket Outlook Object Model (POOM), you can read, create, and modify items that are used by the Pocket Outlook's Calendar, Tasks, and Contacts. In addition, you can access and create cities that the World Clock uses. To access Pocket Outlook objects, the Pocket Outlook Object Model (POOM) SDK is required. You can download the POOM SDK from the following Microsoft Web site:

    http://www.microsoft.com/downloads/details.aspx?FamilyID=78d1a8b7-d606-45b2-9cdc-58bf5a578338

    For additional information about how to use the POOM from eVB, click the following article number to view the article in the Microsoft Knowledge Base:

    265771 How to access Pocket Outlook objects from eMbedded Visual Basic and VBCE

    back to the top
  • Q. Can I call functions in eVB 3.0 applications?

    A. eVB 3.0 allows you to call many Windows CE application programming interface (API) functions directly. eVB ships with an API Text Viewer to view the API information from the Winceapi.txt file. In certain circumstances, because eVB does not support structure data type, you may still need to use eMbedded Visual C++ to create an ActiveX control to wrap the appropriate API calls and then host the control in eVB.

    For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

    209014 How to call Windows CE APIs from VBCE or eVB

    Note You cannot make API calls from VBCE 5.0 applications.

    back to the top
  • Q. Do I need a Windows CE device to run eVB 3.0?

    A. You do not need a device to begin developing eVB applications. You can create and debug Windows CE-based applications from your desktop computer. Built-in emulation technology provides the look and function of a device on your desktop computer. Windows 2000 Professional or Windows NT Workstation 4.0 Service Pack 5 is required to use the built-in emulation technology.

    back to the top

REFERENCES

For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

260080 eMbedded Visual Basic 3.0 release notes

Modification Type:MajorLast Reviewed:3/28/2006
Keywords:kbinfo KB260081
©2004 Microsoft Corporation. All rights reserved.