Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Dependency checking is an integral part of creating a configuration. It is one of the primary methods of adding components, and helps ensure that a run-time image contains all of the components needed to operate correctly. This includes components that may not be known to the user, such as components with visibility below the visibility threshold and components required by the platform.
Dependency checking is a three-step process, repeated for each component in the configuration:
- Discovering the include dependencies of a component.
- Determining whether these dependencies are satisfied by components that already exist in the configuration.
- Resolving all include dependencies that are not yet satisfied.
After you initiate the dependency checking process, Windows XP Embedded Target Designer performs the first two steps. The third step is performed either automatically by Windows XP Embedded Target Designer or manually by the user. This depends on how Windows XP Embedded Target Designer is configured and also on whether choices have to be made to resolve a dependency.
In This Section
- Checking Dependencies
Describes how to use Windows XP Embedded Target Designer to verify that the include dependencies of the components in a configuration have been satisfied, and resolve any that have not. - Manually Resolving a Dependency
Describes how to use Windows XP Embedded Target Designer to resolve the dependencies that are listed on the Tasks tab during a dependency check. - Automatically Resolving Dependencies
Describes how to configure Windows XP Embedded Target Designer to automatically resolve dependencies during a dependency check. - Disabling Auto-Resolve
Describes how to turn off the automatic dependency resolution feature in Windows XP Embedded Target Designer.
Related Sections
- Components in Target Designer
Describes how to use Windows XP Embedded Target Designer to find components in the database, to add components to a configuration, and to work with them once they are added.
See Also
See Include Dependencies for a description of component dependencies that require the presence or absence of other components.
See Component Visibility for a description of the visibility value that is assigned to each component and how it is used and modified by Windows XP Embedded Target Designer.
Last updated on Wednesday, October 18, 2006
© 2006 Microsoft Corporation. All rights reserved.