COM Objects and Pocket PC 2003
-
Hi there. Couldn't decide whether to post this in the Embedded/Mobile forum or the COM forum. Plumped for this one, hope it's reasonably on-topic. I am looking at writing a new Pocket PC 2003 app using the .NET Compact Framework. Pretty excited, as this is a "step up" from using the eVC++ 3.0 tools that I have been using for the past few years. One of the requirements of the new app is that it will have a customised SIP--basically to have much larger key buttons so as to allow entering data using a (fat) finger. On Pocket PC 2002 that I have previously worked on, this involved writing a COM object DLL implementing the
IInputMethodinterface, and having the DLL register itself when installing the CAB. Then, in the actual application, the COM object would be instanciated usingCoCreateInstance(). Using .NET CF, I am not able to write COM objects, is that right? Which means I would have to "drop down" to using eVC++ 4.0 (4.0 rather than 3.0, in order to target PPC2003) to write the COM object. Then, in the .NET CF application, I would need to use a combination P/Invoke and a COM-object-DLL-wrapper to "get at" the custom SIP that I implement in the above DLL. Does this make sense to you, and do you think I'm on the right track? I guess I'm really just asking so that I know what is possible, and to confirm that I am indeed heading in right direction... Any feedback would be much appreciated. Cheers, Jon -
Hi there. Couldn't decide whether to post this in the Embedded/Mobile forum or the COM forum. Plumped for this one, hope it's reasonably on-topic. I am looking at writing a new Pocket PC 2003 app using the .NET Compact Framework. Pretty excited, as this is a "step up" from using the eVC++ 3.0 tools that I have been using for the past few years. One of the requirements of the new app is that it will have a customised SIP--basically to have much larger key buttons so as to allow entering data using a (fat) finger. On Pocket PC 2002 that I have previously worked on, this involved writing a COM object DLL implementing the
IInputMethodinterface, and having the DLL register itself when installing the CAB. Then, in the actual application, the COM object would be instanciated usingCoCreateInstance(). Using .NET CF, I am not able to write COM objects, is that right? Which means I would have to "drop down" to using eVC++ 4.0 (4.0 rather than 3.0, in order to target PPC2003) to write the COM object. Then, in the .NET CF application, I would need to use a combination P/Invoke and a COM-object-DLL-wrapper to "get at" the custom SIP that I implement in the above DLL. Does this make sense to you, and do you think I'm on the right track? I guess I'm really just asking so that I know what is possible, and to confirm that I am indeed heading in right direction... Any feedback would be much appreciated. Cheers, Jon