|
| |
Converting a CE ActiveX Control to a Windows Desktop Version
- Special thanks to Francis
R. Smith, Jr. for contributing to this article. Francis works for Honeywell,
Inc. as Development Engineer currently writing Windows CE software in Visual C++ 6.0.
|
| Overview It is a fact that Windows CE now has support for ActiveX
controls. After you create a CE ActiveX control, you will come across the all too common
problem of inserting the control into your VB application. This occurs because the CE
ActiveX control is not registered in your desktop registry so it won’t be available
in the Components List! Therefore you will not be able to insert it into your CE
application.
To solve this problem, you must create 2 versions of
your CE control! The 1st version will be your CE ActiveX control, typically
created with Visual C++ (ATL/MFC/Win32). This version is the code that gets put into the
emulation environment and on the CE device. The 2nd version that needs to be
created is a Windows desktop control. This control will be created for a Win 32
environment. The desktop version of your CE ActiveX control is basically just a shell for
telling VBCE/VCCE the names of the events/methods/properties that are exposed by the
control.
Converting the CE ActiveX control to a Windows desktop version
is a step by step process and I have outlined this process below.
Show me the steps...
Download Entire Document |
"The key to making a Windows CE ActiveX
control is creating 2 versions of the control." |
|
Dev Corner
