Comments on: Entity Framework 4 – Entity Dependency Injection

By: John

John — Tue, 02 Jun 2009 22:04:32 +0000

(Feel free to move this to a post about EvoLisa) Could you by any chance share the source, or at least a binary, of your current fastest EvoLisa implementation (Dotfuscate it if you must)? I think I can beat it by a long way… My current implementation runs the first 5000 generations (with default settings) in 10 seconds on a Single Core of a Pentium 4 from 2004, and it continually runs 200-250 gen/sec with constraints of 50 polygons, each with 5 points (which keeps the performance consistent). The WPF port didn’t work out that well (I didn’t even try that hard, since RenderTargetBitmaps perform about the same function as your Renderer). I may still be able to speed it up to over 2000 (!!!) continuous generations per second on that same P4, and in the process make the code Embarrassingly Parallel, by using something a little more Direct to render the polygons. Once I do that, the major bottleneck will be the Fitness Function again, and I have a few tricks up my sleeve to improve that further (IL tell you more later). I think 1,000,000 generations in 15 seconds on a brand-new Core 2 Quad will be easily doable (more on that before summer’s end). Just e-mail me (starcalc AATT gmail DDOOTT com) if you want my further-improved source code and binary. Oh, and BTW, I’ve removed the need for cloning the drawing every generation by using a list of ints to track the changes.

By: Keith Patton

Keith Patton — Sun, 31 May 2009 00:49:40 +0000

Interesting, however i think if you have the need to inject services relating to email or other infrastructure needs, this is probably best done within the Application layer (in DDD terminology) rather than the core domain layer which should not involve itself with sending emails.

I’ve created a post on how to implement a DDD driven architecture with EF including Dependency Injection here if you are interested:
http://blog.keithpatton.com/2009/05/30/Entity+Framework+POCO+Repository+Using+Visual+Studio+2010+Net+40+Beta+1.aspx

By: Sebastian Markbåge

Sebastian Markbåge — Sat, 30 May 2009 20:05:28 +0000

Cool stuff. Probably a better for .NET than NHibernate’s interceptors.

I prefer to keep my service references outside of my entities though. But DI and use of Services is a big hassle in DDD that can mess up an otherwise clean domain model.

I’ve tried to address this using what I’ve called transitory domain objects. I use them in front of the entities.

http://blog.calyptus.eu/seb/2009/05/transitory_domain_object/

By: Transitory Domain Objects - Calyptus Life

Transitory Domain Objects - Calyptus Life — Sat, 30 May 2009 19:54:38 +0000

[...] A common problem with DDD is the injection of services to your domain model. Sometimes your domain relies on external services to do it’s job. You could do that by injecting your services directly to your entities using NHibernate Interceptors or ObjectStateManager for Entity Framework v4. [...]