Extendable View Model
Overview
ExtendableViewModel<TSelfInterface> is a generic abstract class that extends RoutableViewModel and adds support for dynamic extensibility. It allows your view model to be extended with additional features.
How It Works
MEF2 discovers your view model and looks for implementations of
IExtensionFor<TSelfInterface>.Each extension is instantiated and added to the
Extensionscollection.The
Initmethod is called automatically. It invokes each extension'sExtendmethod, passing your view model and its disposable container.AfterLoadExtensionsis called to allow for any final setup in your view model.
Core Components
Generic Parameter
The TSelfInterface generic parameter specifies the interface that your view model implements (or the view model type itself).
IExtensionFor Interface
Your extensions should implement the IExtensionFor<in T> interface, which contains a single method:
This method is called when the extended view model is initialized.
context: Represents the view model itself.contextDispose: The CompositeDisposable container of the view model.
You can register your IDisposable objects with it. Additionally, if your extension class implements IDisposable, the view model will automatically register it to the CompositeDisposable.
Extensions Collection
The Extensions property contains all imported extensions for your view model:
These are automatically discovered and imported by MEF2 at startup.
Initialization and Loading
The Init method is called automatically by MEF2 when all imports have been satisfied:
It iterates through extensions and calls the Extend method with your view model (returned by GetContext) and the view model's CompositeDisposable.
You must implement the abstract AfterLoadExtensions method to perform any initialization required after extensions are loaded:
You can leave this method empty if no post-initialization logic is needed.
Example
A basic usage example is our Home Page. When adding pages to an app using Asv.Avalonia, you will likely create an Extension for IHomePage so your page is accessible from the home tools menu.
These extensions look like this:
In this example, we add a new tool to the home page that opens the LogViewer page. We export an extension for the IHomePage interface, which is implemented by HomePageViewModel. The interface contains the Tools collection, which we modify.
API
ExtendableViewModel<TSelfInterface>
Represents a base class for a view model that supports extensibility using MEF2. This class provides a mechanism to load and apply extensions dynamically.
Property | Type | Description |
|---|---|---|
|
| Gets or sets a collection of extensions that enhance the functionality of the view model. Extensions are lazily imported using MEF2. |
Method | Return Type | Description |
|---|---|---|
|
| Called when MEF2 has completed importing dependencies. This method initializes and applies all available extensions to the current instance. |
|
| Gets the current instance as |
|
| Called after all extensions have been loaded and applied. Derived classes must implement this method to provide additional logic after extension loading. |
IExtensionFor<T>
Defines a contract for an extension that can be applied to a specific type T. This interface allows modular enhancements to be dynamically applied to existing objects.
Method | Return Type | Description |
|---|---|---|
|
| Applies the extension logic to the given context. |
IExtensionFor<T>.Extend
Parameter | Type | Description |
|---|---|---|
|
| The target object to extend. |
|
| Disposable collection, that disposed with context. |
ExportExtensionForAttribute<T>
Marks a class as an exported extension for a specific type T. This attribute is used with the Managed Extensibility Framework (MEF2) to enable automatic discovery and composition of extensions.