How it works
SPDepend checks the code for all dependencies between artifacts, for instance:
- Content Type inheritance
- Dependencies to external webservices / REST endpoints
- Relation between ListInstance and Lists
- referenced images or files
It also shows dependencies to SharePoint elements or to third party elements (e.g. dependent Features, ContentTypes, Assemblies etc.) helping to make sure that all required elements are installed on the target environment.
Ensure Maintainable Structure
Architects use the dependency diagram to check the Sharepoint code for circular dependencies or unneeded dependencies between packages. This helps to ensure a proper solution design and a maintainable structure.
Check for required components
The SharePoint administrators can use the dependency report before installation of the WSPs or Add-ins in SharePoint to ensure that all required SharePoint or third party components are installed.
If a WSP or Add-in package depends for instance on a specific version of an assembly the IT Pro can check if this required element is installed and activated.
Check Impact after Code Changes
During development of a SharePoint customization the dependency diagram can help to make an impact analysis for code changes.
If a core component was changed the diagram can highlight all dependent components which may be impacted by the change.
Validate Sequence of Deployment Process
Administrators or architects can use the dependency diagram to validate the order in which the WSPs need to be installed.
The component without dependencies to other WSP or Add-ins needs to be installed first, then a chain of all next WSPs can be taken from the diagram.