Modularity for UniversalApps

Allow multiple SKUs of your Universal App with loosely coupled modules. Works with P&P Prism, Caliburn Micro, etc… and other MVVM frameworks.

Feel free to reuse in your application as-is.

Microsoft.TED.WinRT.Modules

Adds a ModuleManager class that loads dependencies in a definable order.

ModuleManager manager = new ModuleManager();
manager.AddModule(name: "CarModule", entryPoint: "Module1.Module, Module1", dependsOn: new[] { "VehicleModule"});
manager.AddModule(name: "TruckModule", entryPoint: "Module2.Module, Module2", dependsOn: new[] { "VehicleModule"});
manager.AddModule(name: "VehicleModule", entryPoint: "Module3.Module, Module3", dependsOn: new[] { "DatabaseModule"});
manager.AddModule(name: "BoatModule", entryPoint: "Boats.Module, Boats", dependsOn: new[] { "DatabaseModule"});
manager.AddModule(name: "DatabaseModule", entryPoint: "DB.Module, DB");
await manager.InitializeAsync();

Each Module has an EntryPoint class, that is being called on initialization:

public class Module : IModule
{
    public async Task InitializeAsync()
    {
       // ...
    }
}

The order in which the modules are initialized is automatically resolved..

Microsoft.TED.WinRT.ModularHub

A WinRT Hub derived control, that can be extended from losely coupled modules.

1. Each Module can add content to a global hub, via an IHubMetadataService singleton:

_hubMetadataService.AddHubSection("M2", "Cats", typeof(CatListView).AssemblyQualifiedName);

2. Place the hub in a page & bind it:

<hub:ModularHub ItemsSource="{Binding HubSections}"/>

3. Use the IHubMetadataService singleton to fetch the hub sections from modules in the ViewModel

this.HubSections = new ObservableCollection<HubMetadata>(_hubMetadataService.GetSections());