Within the Compact 2013 environment, application can be created using one of the following options:

1.     Managed code in C#, as a Visual Studio 2012 application project

2.     Managed code in Visual Basic, as a Visual Studio 2012 application project

3.     Native code in C++, as a Visual Studio 2012 application project

4.     Native code in C or C++, as a Platform Builder subproject

5.     XAML for Windows Embedded Compact application

There are two different transports (connectivity) needed to support the debugging environment associated with the above application development options, as follow:

·         Core Connectivity (CoreCon)

·         Kernel Independent Transport Layer (KITL)

CoreCon to Support Managed and Native Code Application Development

To support and debug managed and native code application development, as a Visual Studio application project, in addition to the SDK generated from the OS design for the target device, required software library and OS component, CoreCon files under the following folder must be placed in a file system that is accessible by application launch from the OS runtime imagine, running on the target device:

C:\Program Files (x86)\Common Files\Microsoft Shared\Embedded Tools\CoreCon\11.0\Target\wce800\

CoreCon is needed to deploy VS 2012 managed and native code application to a Compact 2013 target device.  Detail CoreCon implementation to support application development is covered in section IV, application development.

KITL to Debug Platform Builder Subproject Application Development

To debug native code application development as a Platform Builder subproject, in addition to adding the required software library and OS component to the OS design, the OS runtime image must be built with KITL enabled.

The debugging facility for Platform Builder subproject application is the same as debugging an OS design.

KITL is not needed to create and deploy a Platform Builder subproject application.  A Platform Builder subproject application is compiled as part of the OS runtime image and deploy to the target device along with the OS runtime image.  KITL is needed to debug Platform Builder subproject application.

KITL to Support XAML for Windows Embedded Compact Application Development

A XAML for Windows Embedded Compact application is built and compiled as a Platform Builder subproject application.  The application binary is compiled as part of the OS runtime image and deploy to the target device along with the OS runtime image.

Similar to the Platform Builder subproject application, KITL is not needed to create and deploy an XAML for Windows Embedded Compact application.  KITL is needed to debug the application.