The dependency checker examines the target PBLs and output assemblies in a WPF Window Application project, and displays information about the dependencies among the assemblies.
For any group of PBLs built to an output assembly, the dependency checker might detect single dependencies on other assemblies, circular dependencies, or no dependencies. A group of PBLs might be dependent, in turn, on a PBL that is built to the executable file.
The Dependencies tab of the WPF Application Project painter contains a list of output assemblies and their dependencies, in build order. If you change output assemblies in the Assemblies page, the dependency checker displays a note on the Dependencies tab, advising you to run Check Dependencies to update dependencies. This command is available in
A project build uses the current build order. Therefore, if you launch a build after changes that affect dependencies, the build can fail with dependency errors. Dependencies can change because you changed assemblies in the project, or through code refactoring. You might try to resolve dependency errors by refactoring, or you can invoke the dependency checker to update the build order.
The dependency checker displays any compiler errors in the Output window and Error List. If there are no compiler errors, the Assembly Dependencies window opens, where you can examine dependencies in detail.
The top of the Assembly Dependencies window has a read-only, collapsible key view that explains the format of the information below. The main output area of the window lets you navigate dependencies in detail. It provides expander controls to show or hide any part of the dependency tree, and highlights any dependency errors. You can also double-click a script reference in the tree to navigate to its source.
The Output window notes the progress of dependency checking. For example:
-------- Checking dependencies using project settings -------- Checking project settings... Using Project p_examples_wpf Dependency check complete. Error: output assembly pbexamw1.dll has a dependency on examples.exe Error: There is a circular dependency between pbexamw1.dll and pbexamuo.dll Time elapsed for dependency check: 00:00:08.3593750 -------- Dependency check finished ---------
These output messages indicate the status of the dependency check: