Share via

Application Development with an Imported SDK (Windows Embedded CE 6.0)

  • Article

1/5/2010

A software developer can import an SDK created by using Platform Builder into the following Visual Studio editions:

  • Standard
  • Professional
  • Team Edition
  • Team Suite
  • Team Foundation Server

Then, a software developer can use the SDK to create applications that run on the Windows Embedded CE–based run-time image from which the SDK was exported.

Important

This topic applies to an older product version. See documentation for the most current version of Windows Embedded Compact. Or visit Windows Embedded Products & Solutions for the latest information about intelligent systems powered by Microsoft.

Overview of SDKs for Windows Embedded CE

An SDK for Windows Embedded CE is created by the OEM of a target device. It must provide a set of APIs that a software developer can use to develop software applications for the target device. An SDK may provide APIs that were imported from Platform Builder for CE 6.0 or custom APIs that are developed by the OEM. Information about APIs that were imported from Platform Builder for CE 6.0 is available in the CE 6.0 documentation.

The SDK should also support a set of development frameworks that you can use to design your applications, such as Microsoft Foundation Classes (MFC) for Windows Embedded CE, or Active Template Library (ATL) for Windows Embedded CE. Contact the OEM to find out which APIs and development frameworks are supported by the SDK.

Tools for Application Development

When you develop applications for a target device, you will use the tools in Visual Studio 2005. MSDN provides various resources for developing smart device applications by using Visual Studio 2005. For more information about smart device application development, see Getting Started with Smart Device Projects.

Testing an Application

To test an application, you must download it to the target device that is either a standard development board or CEPC. First, you must establish a connection between Visual Studio 2005 and the target device. For more information, see How to: Connect to Windows CE Device Without ActiveSync.

To enable software developers to test and debug client applications, you can distribute standard development boards to your software developers. Standard development boards include the microprocessor and hardware components for your thin client, together with a board support package (BSP) for the Windows Thin Client OS design. Developers can assemble the standard development boards and connect them to their desktop computers by using a cable. Then, developers can build and download applications from Visual Studio 2005 to the standard development board for testing and debugging.

For more information about standard development boards, see Standard Development Board Design.

If you do not have a target device, you can also use the Device Emulator in Platform Builder for CE 6.0 as a virtual hardware platform that you can use to test applications on your run-time image. For more information, see Device Emulator.

See Also

Other Resources

Developing an Application
SDK Development
How to Add an Application to the Catalog
How to Develop an Application for a CEPC