Greetings.
I'm trying to create a framework for running automated tests against a device that uses Windows Embedded CE. Ideally, the framework will connect to the device, run scripts provided by myself or other testers, log the results, and do this all without
user intervention. So far, out of the frameworks I've looked at to code against for this, I've found the following:
* Smart Device Connectivity SDK throws an exception every time I try to connect to the device, claiming that ActiveSync is not installed. Whilst this is true, the powers that be chose not to include ActiveSync support in the ROM image. Since
some of my automation would really enjoy a way of deploying files to the device without having to modify XSL files, the Microsoft.SmartDevice.Connectivity SDK or something similar would have been handy.
* Remote Tools Framework - This seems to take a dependency on the Remote Tools Shell, which would make it impossible to integrate into, say, a build process or have the tests triggered on, say, a new ROM image being available.
* CoreCon - Does almost precisely what I need it to do (even lets me launch processes and modify the on-device registry to automate, say, screen calibration), but seems to be a trifle ... documentation impaired. Also, is it depricated or is it not
depricated? The Windows Embedded CE relnotes seem to claim that the CoreCon HLAPI (what's a HLAPI?) is depricated, but a search or five on CoreCon tells me that Windows Phone 7 devtools are using it under the hood.