The current NotifyPropertyChangedBase implementation requires clients to inherit in order for them to enjoy the INPC functionality.
While this may seem suitable for FE cases there are different flows that should be supported for the BE and specifically Domain Layer.
Thus the functionality must be wrapped in a reusable fashion and become consumable via composition.
A natural candidate is NotifyPropertyChangedCore implementation

There are cases, especially with advanced licensing and modularity scenarios where the same feature module would include different components based on several areas. Each one of the components would have its own root view model and would be identified by area/region identifier.

Add examples including the following scenarios:

• Simple flat structure usage
• Simple licensing
• Multiple root view models (see the respective component-oriented issue)
• Advanced licensing including different components