Comments on: Event Aggregation http://davybrion.com/blog/2009/10/event-aggregation/ inquisitive: adjective. given to inquiry, research, or asking questions; eager for knowledge; intellectually curious Tue, 22 May 2012 17:40:00 +0000 hourly 1 http://wordpress.org/?v=3.3.2 By: MVP In Silverlight/WPF: Some Infrastructure Bitshttp://davybrion.com/blog/2009/10/event-aggregation/comment-page-1/#comment-101126 MVP In Silverlight/WPF: Some Infrastructure Bits Sat, 03 Sep 2011 17:09:36 +0000 http://davybrion.com/blog/?p=1708#comment-101126 [...] Aggregation through an Event Aggregator. I've covered this before, so i'm just going to link to my old post about it. In the sample that accompanies this series, you'll find the code for the Event Aggregator and [...] [...] Aggregation through an Event Aggregator. I've covered this before, so i'm just going to link to my old post about it. In the sample that accompanies this series, you'll find the code for the Event Aggregator and [...]

]]> By: kilfourhttp://davybrion.com/blog/2009/10/event-aggregation/comment-page-1/#comment-22719 kilfour Thu, 15 Oct 2009 13:14:46 +0000 http://davybrion.com/blog/?p=1708#comment-22719 After using the EventAggregator for a couple of days now, I have to agree with putting the event declarations in a seperate namespace. ;-) Deciding to put them near the receiver, or near the one that calls publish, and what to do if the event gets thrown by different classes, induced a headache. So an 'Events' namespace it is. After using the EventAggregator for a couple of days now, I have to agree with putting the event declarations in a seperate namespace. ;-)
Deciding to put them near the receiver, or near the one that calls publish, and what to do if the event gets thrown by different classes, induced a headache.
So an ‘Events’ namespace it is.

]]> By: Reflective Perspective - Chris Alcock » The Morning Brew #452http://davybrion.com/blog/2009/10/event-aggregation/comment-page-1/#comment-22682 Reflective Perspective - Chris Alcock » The Morning Brew #452 Mon, 12 Oct 2009 07:42:30 +0000 http://davybrion.com/blog/?p=1708#comment-22682 [...] Event Aggregation - Davy Brion explores the concepts and implementation of Event Aggregation Patterns for use in communicating occurrences to other parts of the code without caring about what those other parts are. [...] [...] Event Aggregation – Davy Brion explores the concepts and implementation of Event Aggregation Patterns for use in communicating occurrences to other parts of the code without caring about what those other parts are. [...]

]]> By: Davy Brionhttp://davybrion.com/blog/2009/10/event-aggregation/comment-page-1/#comment-22681 Davy Brion Mon, 12 Oct 2009 07:00:33 +0000 http://davybrion.com/blog/?p=1708#comment-22681 @Kilfouri sort of agree on that... but the ability to type "Events" + "." and have all the event types show up is pretty handy ;) @Kilfour

i sort of agree on that… but the ability to type “Events” + “.” and have all the event types show up is pretty handy ;)

]]> By: kilfourhttp://davybrion.com/blog/2009/10/event-aggregation/comment-page-1/#comment-22680 kilfour Mon, 12 Oct 2009 06:57:14 +0000 http://davybrion.com/blog/?p=1708#comment-22680 Nice implementation. Just a thought on <i>simply be grouped in separate namespaces/folders</i>. I feel it's better to put classes in the namespaces where they are used, and I try to avoid using namespaces based on language features. I've seen too many projects with an interfaces namespace, events namespace, views namespace, etc... Which usually means that if you're working on one thing, you need a corresponding other thing in each of the other namespaces. Nice implementation.
Just a thought on simply be grouped in separate namespaces/folders. I feel it’s better to put classes in the namespaces where they are used, and I try to avoid using namespaces based on language features. I’ve seen too many projects with an interfaces namespace, events namespace, views namespace, etc… Which usually means that if you’re working on one thing, you need a corresponding other thing in each of the other namespaces.

]]> By: Davy Brionhttp://davybrion.com/blog/2009/10/event-aggregation/comment-page-1/#comment-22671 Davy Brion Sun, 11 Oct 2009 15:33:37 +0000 http://davybrion.com/blog/?p=1708#comment-22671 definitely not an assembly per component... i use as few assemblies as possible: http://davybrion.com/blog/2008/07/many-projects-dont-lead-to-a-good-solution/I expect most of the events will simply be grouped in separate namespaces/folders and that's about it. definitely not an assembly per component… i use as few assemblies as possible: http://davybrion.com/blog/2008/07/many-projects-dont-lead-to-a-good-solution/

I expect most of the events will simply be grouped in separate namespaces/folders and that’s about it.

]]> By: Benny Michielsenhttp://davybrion.com/blog/2009/10/event-aggregation/comment-page-1/#comment-22670 Benny Michielsen Sun, 11 Oct 2009 13:30:00 +0000 http://davybrion.com/blog/?p=1708#comment-22670 How do you structure your project for the events themselves? Do they come in a single assembly, an assembly per component (SalesEvents, OrderEvents,...) How do you structure your project for the events themselves? Do they come in a single assembly, an assembly per component (SalesEvents, OrderEvents,…)

]]>