Dependencies

A dependency is a requirement of one component upon another component. Dependencies can either cause the inclusion or exclusion of other components, or control the relative order in which components are built during the run-time image build process. This allows a component to be as small as possible while ensuring that it has all of the resources it requires to run correctly. A dependency can be expressed upon a single component or upon a group of components known as a dependency group.

Dependencies are specified in the definition of the dependent component. For example, if component A requires that component B be built before it and also requires the presence of component C, the definition of component A must contain a build order dependency upon component B and an include dependency upon component C.

Dependencies can be disabled with Component Designer. This is useful if you want to remove a dependency, but keep it available for use at a later time. If a dependency is disabled, Target Designer disregards the dependency during the dependency checking process and the build process.

In This Section

• Include Dependencies
  Describes dependencies that require the presence or absence of other components.
• Build Order Dependencies
  Describes dependencies that require that one component be built before another during the run-time image build process.
• Components Re-factoring
  Describes the re-factoring of components to enable footprint reduction.

Related Sections

• Components
  Describes the individual units of functionality that make up a run-time image and the benefits of creating and using them.
• Dependency Groups
  Describes a type of group that collects components for the purpose of allowing dependencies on entire groups of components, or selected members therein, rather than on individual components.

Last updated on Wednesday, October 18, 2006

© 2006 Microsoft Corporation. All rights reserved.