Understanding the Alliance Business Suite dependency tree

The Alliance Business Suite is designed as a set of Application Layers dependant upon their service predecessor. Each Layer constitutes a Component for the Alliance Business Suite.

Components can be provisioned as Standalone Applications or used as stand-alone libraries. This means that it is possible to bring the Alliance Business Platform (FenixAlliance.ABP.*) into a new/existing application without having to include any dependency from the Alliance Business Studio (FenixAlliance.ABS.*). The same is true for the Alliance Business Model (FenixAlliance.ABM.*), which can be included without any reference to the Alliance Business Platform namespace (FenixAlliance.ABP.*).

Components rely on their Service Predecessor through abstractions, allowing customers to override almost every functionality through custom implementations.


Note: Because other services on the Alliance Business Suite instance might rely on default implementations performing some work, it is imperative for customers who bring their own implementations to make sure their implementations stay compliant with each specification.

Understanding external dependencies

External dependencies required by the Alliance Business Suite are bounded to the Alliance Core Libraries Component, which means that they are available to every dependant Component due to .NET's Waterfall Dependency Resolution mechanism.

This means that Web Contents can make use of already present libraries such as Radzen Blazor, MudBlazor, Newtonsoft.Json, and many more. For a more detailed list of dependencies, please refer to the Core Dependencies.