Microsoft KB Archive/260101

= INFO: Installation Issues Regarding eMbedded Visual Basic 3.0 =

Article ID: 260101

Article Last Modified on 9/4/2002

-

APPLIES TO


 * Microsoft eMbedded Visual Basic 3.0

-



This article was previously published under Q260101



SUMMARY
This article discusses known issues concerning the installation of eMbedded Visual Basic (eVB).



MORE INFORMATION
Side-by-Side Visual Studio 6.x Installation Issues

To develop for HPC Pro and Palm-size PC 1.2 devices, you must install the new Microsoft Windows CE SDKs for those platforms; these SDKs are included with eMbedded Visual Tools. To develop for the Pocket PC, you must install the new Windows CE SDK for this platform as well.

If you install Microsoft Windows CE Toolkit for Visual Basic (VBCE) 6.0 after installing eMbedded Visual Basic 3.0, the new HPC Pro SDK is replaced with the old one. You have to re-install the new HPC Pro SDK.

If you uninstall VBCE 6.0 after installing eMbedded Visual Basic 3.0, the HPC Pro SDK is removed. To develop for this platform, you must re-install the new HPC Pro SDK.

Uninstalling Either VBCE 6.0 or eMbedded Visual Basic 3.0 Leaves Design-time ActiveX Controls Unregistered

Workaround:

If VBCE6.0 has been uninstalled, then reinstall eMbedded Visual Basic 3.0.

If eVB3.0 has been uninstalled, then reinstall VBCE 6.0.

The Microsoft SDK for Windows CE for the Palm-size PC 1.2 and Handheld PC Professional Edition 3.0 Share the MSceadodt.dll file.

If you install both SDKs and then uninstall either one, you need to reinstall the remaining SDK in order to continue using ADOCE with that SDK, because they both share MSceadodt.dll.

