lwork
asked on
Windows CE 5.0 or Windows Mobile 5.0 for application development?
We are going to develop software to be run on a mobile scanner which offers both Windows CE5.0 and Windows Mobile5.0 as the OS options.
The device will use a cell phone and Bluetooth connection to transmit the data back to a server.
The devices don't need to be used as PDAs, just to scan and run the application we develop.
We are leaning towards Windows CE5.0 as the OS, but would like to know if there are any reasons Windows Mobile5.0 would be a better or safer choice.
What are some of the development issues we should be aware of when developing an application for Windows CE5.0?
The device will use a cell phone and Bluetooth connection to transmit the data back to a server.
The devices don't need to be used as PDAs, just to scan and run the application we develop.
We are leaning towards Windows CE5.0 as the OS, but would like to know if there are any reasons Windows Mobile5.0 would be a better or safer choice.
What are some of the development issues we should be aware of when developing an application for Windows CE5.0?
ASKER
Development will be VB.
I understand Moblie 5.0 is more popular (because users can use more robust PDA aspects), but I've heard it also has more constraints as to what can run on it and be installed.
I understand Moblie 5.0 is more popular (because users can use more robust PDA aspects), but I've heard it also has more constraints as to what can run on it and be installed.
well, there is the security model from Microsoft which demands signing the executables and dlls - this is applicable mostly to smartphones, so that's not fully your case. anyway, all this security policy is controlled by registry settings which may be changed. usual result of all above is that the user is prompted with "Unknown Publisher" message when you try to run the application 1st time (and for every new version too)
I haven't heard about such behavior on WinCE50, but I assume it depends on the vendor as by far not all WM50 PDAs have security policy turned on.
I haven't heard about such behavior on WinCE50, but I assume it depends on the vendor as by far not all WM50 PDAs have security policy turned on.
well mobile scanners are more popular running CE than Windows Mobile. With ce you will have alot more oprions vs Windows Mobile.
I wonder which ones?
try looking at the Symbol's
Also the CE devices support plug and play
Also the CE devices support plug and play
ASKER
>With ce you will have alot more oprions vs Windows Mobile.
Such as?
This is exactly what I'm trying to figure out.
Such as?
This is exactly what I'm trying to figure out.
to Mikal613: I was curious about options unavailable in Windows Mobile in comparison to WinCE 50
Symbol devices are usually rugged and therefore expensive, Intermec ones too. There are many different devices with scanners, some of them have WinCE, some - Wm, and Symbol here is good example having models of both types
There are also Socket scanners which are pluggable to the PDA without scanner, e.g. iPaq
Symbol devices are usually rugged and therefore expensive, Intermec ones too. There are many different devices with scanners, some of them have WinCE, some - Wm, and Symbol here is good example having models of both types
There are also Socket scanners which are pluggable to the PDA without scanner, e.g. iPaq
ASKER
I have already decided on the hardware, just not which OS to have installed which is what I'm trying to do now.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
one thing I didn't say is because the code is being build for the compact frame work, providing you have the drivers and libraries for the relevant devices, surly the code would work just as well on both devices, that's the point of the shared runtime.
The one other advantage of CE is the hidden UI which is a pain in the arse with an application that just needs to run and not be interupted or giving it to a non techy user.
The one other advantage of CE is the hidden UI which is a pain in the arse with an application that just needs to run and not be interupted or giving it to a non techy user.
Main problem with CE50 is that there is no convenient emulator for it, and Wm50 comes with it in various modifications. You may also need special SDK from the vendor in you are going to develop in C++