Share via

Checking and Resolving Dependencies

  • Article

Checking and resolving dependencies are important tasks when working with runtime images. The process for doing these tasks in XPECMD is not very intuitive. You must first call the Configuration.CheckDependencies and Configuration.ResolveDependencies commands, and both of these commands require a parameter. This parameter specifies how verbose the output is during each process. You can use the following options to specify verbosity of the output:

  • 0 = Full output
  • 1 = Percent complete, errors and warnings
  • 2 = Errors and warnings only

The following example shows how to do this:

xpecmd> cfg.ResolveDependencies 2
xpecmd> cfg.CheckDependencies 2

Checking dependencies points out any errors and warnings including missing dependencies. However, it does not provide very detailed information.

Resolving dependencies is an automatic process. Simply issue the command and let it run and all of the dependencies that can be auto-resolved will be resolved. You may run into conflicts between components while using these commands. However, XPECMD will only notify you that a conflict has occurred, but will not be able to give you more information on how to resolve the conflict. If you do not know what the conflict is and have resolved it ahead of time, Microsoft recommends that you use Target Designer to resolve these conflicts.

Last updated on Wednesday, October 18, 2006

© 2006 Microsoft Corporation. All rights reserved.