Lazycoder

Persistence Ignorance in the Entity Framework – MSDN Forums

Persistence Ignorance in the Entity Framework – MSDN Forums: “Another question you asked is whether or not the DataContract attributes are necessary, and the answer is that they certainly are not. Our code generation layer supplies them just to make serialization with WCF easier/more automatic with the generated classes. “

I’ll interpret this using my patented Longtime Cynical Microsoft Framework User translator.

Provided you stay on the single, narrow, path we have defined for you when using EF with WCF, a’la ASP.NET and the Page life-cycle, your life will be great. Stray from that path and we will punish you with long, long nights of writing a bunch of baby-sitting code.

Tying it to a base class doesn’t annoy me as much as it does others. It does surprise me. It’s like the LINQ team has never taken a walk around in System.Reflection.

The event-driven dirty flag sounds awfully chatty.

Julia Lerman also has a great post about the different paths to data access in Orcas.
One part caught my eye.

“The second files describes the schema of the database, including pk/fk relationships.”

I’d like to be able to define these relationships even if they don’t exist in the database.