Partager via

Create an OS and SDK for the Sample Virtual Device (Compact 2013)

  • Article

3/26/2014

Because application developers may not have access to the complete set of Windows Embedded Compact 2013 development tools, this topic describes how to create a run-time image and SDK that allows a device to run Compact 2013 without downloading a run-time image from Platform Builder. This particular type of OS design is sometimes called a stand-alone OS or a stand-alone image, because it can be used without a complete installation of Compact 2013.

Create your OS design

In Platform Builder, create an OS design that contains all of the drivers and features your SDK user might need. For information about how to create and modify an OS design, see Design an OS. At a minimum, a test device that runs without Platform Builder requires the following features in the run-time image.

  • At least one communications driver, either a network driver, a USB driver, or a serial port driver.
    • If your SDK user will test on a virtual device, the run-time image must have a network driver.
    • If your SDK user will be running Application Builder for Visual Studio alone, the communications drivers must all be TCP/IP-based (Ethernet, USB RNDIS, Serial RNDIS).
  • Storage and file system drivers, such as ATAPI drivers, USB function support, or any other file system you expect to need.
  • Drivers for any user input or HID devices, such as a keyboard or mouse.
  • Drivers for any additional features.

In addition, be sure to include modules that your SDK user might need, such as the following features:

  • Command shell support.
  • Application development support, such as C++, ATL, or MFC libraries.
  • Features that support UI development, such as Windows Presentation Foundation (WPF).
  • Debugging support.
  • Application debugging support.
  • Remote tools support.
  • Network utilities.

Add the CoreCon files and remote tools framework

A Windows Embedded Compact run-time image that can run without Platform Builder must include the CoreCon files to connect with Visual Studio and Application Builder.

To include the CoreCon files in your run-time image

  1. In Visual Studio, open your OS design, and then go to Solution Explorer.

  2. Under Parameter Files, open OSDesign.bib.

  3. Under the FILES header in OSDesign.bib, add the following files under Name.

    • Clientshutdown3.exe
    • CMAccept3.exe
    • ConmanClient3.exe
    • DeviceAgentTransport.dll
    • eDbgTL3.dll
    • TcpConnectionA.dll

  4. For each file, add the Path by using the following syntax:

    $(ProgramFiles)\Common Files\Microsoft Shared\Embedded Tools\CoreCon\11.0\Target\wce800\{Platform}\{Filename}

    Where Platform is the name of the folder that matches the hardware platform and Filename is the full name of the file including the extension.

  5. For each file, add NK under Memory Type.

    For example, if you are adding the CoreCon files for the x86 hardware platform, your OSDesign.bib file will contain the following lines under the FILES header:

    Clientshutdown3.exe        "$(ProgramFiles)\Common Files\Microsoft Shared\Embedded Tools\CoreCon\11.0\Target\wce800\x86\clientshutdown3.exe"       NK
CMAccept3.exe              "$(ProgramFiles)\Common Files\Microsoft Shared\Embedded Tools\CoreCon\11.0\Target\wce800\x86\CMAccept3.exe"             NK
ConmanClient3.exe         "$(ProgramFiles)\Common Files\Microsoft Shared\Embedded Tools\CoreCon\11.0\Target\wce800\x86\ConmanClient3.exe"         NK
DeviceAgentTransport.dll  "$(ProgramFiles)\Common Files\Microsoft Shared\Embedded Tools\CoreCon\11.0\Target\wce800\x86\DeviceAgentTransport3.dll" NK
eDbgTL3.dll                "$(ProgramFiles)\Common Files\Microsoft Shared\Embedded Tools\CoreCon\11.0\Target\wce800\x86\eDbgTL3.dll"               NK
TcpConnectionA.dll        "$(ProgramFiles)\Common Files\Microsoft Shared\Embedded Tools\CoreCon\11.0\Target\wce800\x86\TcpConnectionA3.dll"       NK

  6. If you also want to include the remote tools framework in this run-time image, see To include the remote tools framework files in your run-time image.

  7. Save and close OSDesign.bib.

To include the CoreCon files in your SDK

  1. In Visual Studio, open your OS design, and then go to Solution Explorer.

  2. Select the SDK that you want to modify, and then go to Properties.

  3. Under Additional Folders, select Add, and then browse to the following folder:

    $(ProgramFiles)\Common Files\Microsoft Shared\Embedded Tools\CoreCon\11.0\Target\wce800\{Platform}

    Where Platform is the name of the folder that matches the hardware platform for this SDK.

  4. Under Target, enter the name of the target folder where you want to store these files in the final SDK, making sure not to include any path information, and then click OK.

  5. If you also want to include the remote tools framework in this SDK, see To include the remote tools framework files in your run-time image.

To include the remote tools framework files in your run-time image

  1. In Visual Studio, open your OS design, and then go to Solution Explorer.

  2. Under Parameter Files, open OSDesign.bib.

  3. Under the FILES header in OSDesign.bib, add the file TCPlatform BuilderootstrapA.exe with the Memory Type of NK and the following Path information:

    $(ProgramFiles)\Microsoft Remote Framework Tools\8.00\target\wce800\{PLATFORM}

    where Platform is the name of the folder that matches the hardware platform for this SDK.

    For example, if you want to add the remote tools framework for the x86 hardware platform, add the following line to your OSDesign.bib file:

    TCPlatform BuilderootstrapA.exe         "$(ProgramFiles)\Microsoft Remote Framework Tools\8.00\target\wce800\x86\TCPlatform BuilderootstrapA.exe"                     NK

  4. Save and close OSDesign.bib.

See Also

Concepts

Use the Sample Virtual Device