Prism event aggregator : Persistent Events

Jun 4, 2015 at 5:24 AM
I have implemented Prism event Aggregators on my server where a service publishes an event and another one listens to it.
My subscription code:
whereas I publish my event as:
The thing is that if the subscriber is alive then, everything works fine. But, lets say an event is published and the subscriber (is a service) somehow shuts down. Is there a way by which when the subscriber comes alive again it can respond to the event that was fired.
I have looked at netmsmq binding and how it provides a queue between services so even if the server shuts down loss of data can be avoided.

Will I have to hook it up with my current mechanism??
Or is there any other way this can be achieved??
And are there any standard mechanisms of handling this?