Comments on: Entity Framework 4 – Managing inverse properties

By: DotNetShoutout

DotNetShoutout — Fri, 22 May 2009 14:24:24 +0000

Entity Framework 4 – Managing inverse properties – Roger Alsing…

Thank you for submitting this cool story – Trackback from DotNetShoutout…

By: Mikael Egnér

Mikael Egnér — Fri, 22 May 2009 12:37:35 +0000

:)
It’s the same in L2S. A bit annoying…

I will stick with your trick and add an obsolete-attribute. I have used the attribute “EditorBrowsable” before to get rid of those properties in the intellisense, but the obsolete-attribute seems much better.
A little fun that “best practice” for a shining new framework may be to use the obsolete-attribute…

By: Roger Alsing

Roger Alsing — Fri, 22 May 2009 11:46:13 +0000

Yes, the “.Order” property of the “OrderDetail” is somewhat of a pain.

It plays badly with the whole idea of POCO, since you most likely wouldn’t have had a “OrderDetail.Order” property at all in a persistent ignorant model.

Luckily, the framework will detect consistency issues and throw if it finds one.
So atleast there is no chanse for such kind of problem to get persisted.

But I don’t think it will be a huge problem as long as you know how to deal with it.

By: Sebastian Markbåge

Sebastian Markbåge — Fri, 22 May 2009 11:13:04 +0000

heh… Ironic. It forces you to add better domain semantics that should’ve been there from the start.

But then it messes things up by exposing potential consistency issues and encouraging you to put logic in OrderDetail that should never have been there.