EventAggregatorLite 1.0.1

EvantAggregatorLite short, step by step tutorial:

1. Create Your event class that implement IBaseEvent interface (You can store all event classes in separate folder MyEvents for example)

using EventAggregator.Interfaces;

public class AddWindowsEvent : IBaseEvent
{
	public string EventDesctiption => "This is AddWindowsEvent desc";
	
	//You can add any code to event class, properties, for instance 
	public string Name{get; set;}
	public List<Windows> WindowsList{get;set;}

}

2. In a class that wants to receive notifications, create a method that takes your event as a parameter (this is a callback method):

public void AddItem(AddWindowsEvent receivedEvent)
{
	//place the code to handle the event here
	System.Diagnostics.Debug.Print($"List of Windows contains {receivedEvent.WindowsList.Count} items");
}

3. Create EventAggregatorLite object and subscribe for Your event(s):

using EventAggregator.Core;

public class VIPClass
{
	private EventAggregatorLite eal;

	public VIPClass
	{
	//create new instance EventAggregatorLite
	eal=new EventAggregatorLite(); 
	
	//set AddItem method to handle AddWindowsEvent events
	eal.Subscribe<AddWindowsEvent>(AddItem); 
	}


public void AddItem(AddWindowsEvent receivedEvent)
{
	//place the code to handle the event here
	System.Diagnostics.Debug.Print($"List of Windows contains {WindowsList.Count} items");
}

}

4. In "sender" class create and configure event instance and publish it:

//create and configure event
IBaseEvent eventToPublish = new AddWindowsEvent();
eventToPublish.WindowsList=new List<Window>();
eventToPublish.WindowsList.Add(new Window());

//publish to all AddWindowsEvent event sybscribers
localEal.Publish(eventToPublish);

5. If You want to unsubscribe just use:

eal.Unsubscribe<AddWindowsEvent>(AddItem);

It's important:

• You must use the same EventAggregatorLite instance in all components that communicate with each other via events (in example above eal and localEal objects refer to the same instance of EventAggregatorLite).
• You can pass EventAggregatorLite instance as constructor parameter, or better, use Dependency Injection container and configure it to resolve EventAggregatorLite as singleton.
• If You want to avoid memory leaks always unsubscribe when removing / dropping objects that have subscribed to some events. This is a very simple EventAggregator that doesn't use weak object references.
• If you need a more professional event aggregator, use, for example, the EventAggregator from the Prism package (from Brian Lagunas and Dan Siegel).