'CoreCon4CE and Autolaunch4CE' Catalog Components for Windows Embedded CE 6.0 and Compact 7 Launhced

When developing app for Windows Embedded CE 6.0 or Windows Embedded Compact 7, you need to establish a connection between your target and your development environment (Visual Studio). To establish the connection and exchange info with the dev tools, WE CE 6.0 and WEC7 leverage a feature called "Core Connectivity" (CoreCon).Usually you would have CoreCon […]

When developing app for Windows Embedded CE 6.0 or Windows Embedded Compact 7, you need to establish a connection between your target and your development environment (Visual Studio). To establish the connection and exchange info with the dev tools, WE CE 6.0 and WEC7 leverage a feature called "Core Connectivity" (CoreCon).

Usually you would have CoreCon binaries downloaded and started automatically by the tools through a connection pre-established like ActiveSync. But if you don't have ActiveSync in your OS image, then you need to download the right binaries on the target and start CoreCon manually… worst: if you've to reboot your image between two debug sessions, you've to redo the whole process.

So developers often set their image to include the corecon components (copied from the VS smart device development files) and automatically start the connectivity at boot time," explains Microsoft.

To facilitate this setup, the embedded101 have released a couple of great powertoy on codeplex that support both CE 6.0 and WEC7 and multiple CPUs.

CoreCon4CE: this Catalog component that adds the right Corecon binaries to your OSDesign.
AutoLaunch4CE: this Catalog component allows to automatically launch the application of your choice.

[tags]wec7,powertoys[/tags]

[Source]