Project Description
CoreCon component for Windows Embedded CE 6.0 and Windows Embedded Compact 7, to simplify the tasks needed to include CoreCon files to the OS image.

  • Update info (Jan. 23, 2014)
If you are looking at this component, consider using the AutoLaunch4CE component instead. CoreCon (same as in this project) is now part of the AutoLaunch4CE component.


To develop application for Windows Embedded Compact and CE 6.0 target device, using Visual Studio, CoreCon connectivity between the Visual Studio IDE and the target device is needed to download the application to the device to testing and debug.

CoreCon files are installed to the development station as part of the Visual Studio installation, to the following directory:
\Program Files\Common Files\Microsoft shared\CoreCon\1.0\Target\WCE400\
There are multiple sub-folders under the above directory, with folder name corresponding to the CPU, each contain separate set of CoreCon files to support a designated CPU.

In order to establish CoreCon connectivity between the Visual Studio IDE and target device, appropriate CoreCon files need to be placed to the device's file system or made accessible from the target device's file system. The CoreCon component, when added to an OS design, help simplify this task, by including batch file script and BIB entries to copy and include the necessary CoreCon file to the compiled OS runtime image. Working in conjunction with the AutoLaunch component, the compiled OS runtime image can be configured to automatically launch CoreCon when the OS starts.

The AutoLaunch component is available from the following URL:

Last edited Jan 23, 2014 at 5:25 PM by Samuelphung, version 4