Windows CE Core or Pro?


Windows CE 5.0 supports two licensing models, Core and Pro, the difference between Core and Pro is defined here – there are a number of components that are in Pro, that includes ActiveSync, Internet Explorer and other components (check the word document or the runtime licensing tool to determine which features you have) – so, how much work do you do to make sure you are keeping within the “Core” functionality of Windows CE ?


– Mike

Comments (5)

  1. Jay Daniel says:

    My company is working on our first WinCE project and have just recently been looking at this issue. It seems that the functionality included in the "core" license is quite extensive enough to meet our needs and so we won’t need the Pro version at all. Only one detail leaves us scratching our heads a bit.

    The component "Standard SDK for Windows CE" is listed as requiring the "Pro" license. What exactly does this mean? Certainly we don’t need to ship an SDK with each operating system image we load to a device. On the other hand, we have about 5 developers who will eventually need an SDK against which to build with eVC++. Would we just need to purchase a Pro license for each of these devleopers? Could you explain the licensing of this component and if we’re just missing the point?

  2. Mike Dimmick says:

    The ‘Standard SDK’ feature brings in a number of components. It simply means that the device will support all the features of the standard SDK, which can be downloaded – a developer can select ‘Standard SDK’ in eVC4 or VS2005 rather than needing the device-specific SDK. In theory any application written to target the standard SDK can be run on any device that implements the standard SDK.

    This common set of components does include some of the components in the Professional stream, so if you included the Standard SDK component in your platform, you would need to pay the Professional licence fee for each device you ship, not just those you ship to developers.

    (How did I do?)

  3. Mike says:

    Mike, spot on! The Standard SDK is a way to be sure that your platform exposes a "well known" set of API’s – if you’re building based on Core then you can still build an SDK from Platform Builder, each of your developers would install the SDK into eMbedded Visual C++ 4.0 or Visual Studio to then start writing applications.

    – Mike

  4. Jay Daniel says:

    Thanks for the clear description, guys. I’m guessing this well-defined functionality includes some of the exposed interfaces from, say IE, and that’s what makes it require the professional edition? As long as the CE-subset of the WIN32 API and various MFC bits are included in the core, I think we’ll be alright. We expect our device to essentially run only our application, so we don’t need to be concerned with end-user ease of development.

  5. Nothing to say, interisting point of view.

    ————————–

    John from <a href=’http://www.go-monaco.com‘>monaco hotels</a> (http://www.go-monaco.com) ***