Domain Event Objects vs Standard Events

"[email protected] [domaindrivendesign]" <[email protected]> 27 May 2015 12:10:32 -0700
Newsgroups gmane.comp.programming.domain-driven-design
Message-ID <[email protected]>
What's everyone opinion on using (assuming .NET) standard custom events as opposed to the traditional DDD way (static domain publisher class)?
 

 sure you are more tightly coupled, but I would think in most instances the client of the domain model is the application layer and this type of coupling is not very harmful. The application layer has enough knowledge for the given use case on how to dispatch the events, in-process, on the bus, in-line, etc.
 

 I don't see many people talking about this approach and I was wondering why? here is some pseudo-code i've been toying around with.
 

             Deferred deferred = new Deferred();
 

             Consignee consignee = new Consignee();
 

             consignee.Created +=
                 (s, e) => deferred.Enlist(() => Bus.Publish(e));
 

             repository.Add(consignee);
 

             deferred.Continue();