If the device has custom API (for I/O or whatever) that typically comes with their SDK, then those would also be missing if you use a different SDK. Likewise, if the target device doesn't have a feature that's in your SDK, you may be able to build and link and app that won't run on the device. Bear in mind that the SDK can "filter" out libs and headers, so if you have a trimmed-down SDK, then you may not have some of the headers and libs you want (though you can always dynamically load the functions you need).
Windows ce 6.0 os image install#
If, for some reason, you can't get an SDK from the OEM then you can install any SDK targeting the same processor and it will work. The SDK, generally speaking, would come from the device OEM. You can circumvent the error you're seeing with a 5.0 target by manually copying the indicated resource CAB to the device and running it before deploying your app. Have you installed a CE 6.0 SDK? I think that's your missing piece. I have found installation processes for building application on VS2005 and WinCE 6.0 and I followed the guide with successful installations. When I attempt to simply target "windows ce 5.0 device" I get errors, for example: Post-deploy error 0x00000001 returned after calling 'Windowswceload.exe /noui WindowsSystem_SR_enu.cab'. The only devices I am able to target are: My problem is that I cannot target WinCE 6.0 when I debug. I have done a lot of digging and it seems a large amount people have a similar difficulty but it's caused by a broad range problems and if there are any solutions, none of them have helped me so far. I'm trying to debug an application of mine on a device running Windows CE 6.0.
Firstly, I'm running VS2005 SP1 and Windows 7 Ultimate.