Components (Windows Embedded Standard 2009)

  • Article

4/23/2012

Components are the self-contained units of functionality that, when combined, describe all of the features of a run-time image. Components can include core and extended properties, resources such as files and registry keys, scripts, group memberships, component Help, and a list of dependencies upon other components. Every component designates a repository or repositories, from which its files can be copied at build time, and a prototype component from which it inherits properties and resources. Components are saved in .sld files and imported into the component database.

Components are intended to be as small as possible. Depending on the requirements of your embedded scenario, a simple component might set one registry key, and a complex component might describe an entire feature such as Internet Explorer. Typically, components are used to define applications, services, and device drivers.

Note

The term component does not refer to a COM+ component, a COM object, a Windows Script Host component, a Windows Installer component, or any other existing Windows programming technology.

In This Section

  • Benefits of Componentization
    Describes how componentizing reduces run-time image footprint and allows for greater performance and reliability and a more secure and customized operating system.
  • Component Visibility
    Describes the visibility value that is assigned to each component and how it is used and modified by Target Designer.
  • Component Types
    Describes the different types of components that can be added to configurations.
  • Dependencies
    Describes inter-component relationships that ensure that a run-time image contains all necessary components and is constructed in the correct order. This includes instructions on handling dependencies of re-factored components that enable footprint reduction.