Emulator Usage Scenarios (Windows CE 5.0)
Whether you are a developer designing an OS based on Windows CE or an application developer targeting the OS, you can use the Emulator to make your work more efficient.
As a developer designing an OS, you can use the Emulator from within Platform Builder and include the Emulator in your SDK. You can customize the Emulator that you deliver with your SDK in the following ways:
- You can emulate custom hardware by taking advantage of a DMA transport, thereby enabling applications to target the same drivers that are in your physical target device.
- You can use the skinning model for the Emulator to mimic the appearance and behavior of a target device for the benefit of application developers and end users. For more information, see Emulator Skin.
If you use the Emulator in Platform Builder, you can support KITL in your run-time image. With KITL support, you can debug your run-time image during development. In Platform Builder, you typically use the Emulator with a run-time image that supports KITL.
However, if you create a run-time image as part of an SDK, do not support KITL in the run-time image. Supporting KITL in the run-time image can cause problems if you do not have access to Platform Builder. If you do support KITL in a run-time image, the Emulator blocks the development tools as it launches, and then waits for a KITL connection with Platform Builder that cannot be made.
As an application developer, you rely on the Emulator delivered with the SDK. Using an SDK that includes a run-time image built for the Emulator, you can develop and test applications while the physical target device is being developed.
Send Feedback on this topic to the authors