![]() ![]() This is made really easy for the OEM through the use of catalog items in Platform Builder. Windows CE OEMs not only add their own Win32 libraries, but in a lot of the cases, they choose not to add certain Microsoft libraries. The Windows CE aspect of this scenario is greatly magnified. Symbol, Intermec, HHP, etc.), all of which the average mobile developer is keen use in their latest application. ![]() With each revision of Windows Mobile, new Win32 APIs and extensions to existing APIs emerge from Microsoft and sometimes OEMs add their own domain-specific APIs (e.g. ![]() At the time of writing this, there exists several hundred variants of Windows Mobile devices, and thousands, if not tens of thousands, of Windows CE devices.įrom the Windows Mobile aspect of the industry, the devices could be running anything from Windows Mobile 2003 to Windows Mobile 6.1 (I have no doubt that there are even a few Pocket PC 2002 devices still in use today). NET Compact Framework applications.īefore I get into the details of the new API, it is always good to have an understanding of the problem we're attempting to address. It's worth noting at this point that I will assume we're only dealing with. I've just added a new helper class to the Smart Device Framework that is designed to determine whether a particular Win32 library exists, and whether it exports a specific entry point. You can check programmtrically a specific dll exist in the device. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |