Adding a Business Layer to ADO .NET Entity Framework?

I don't have experience with LINQ to Entities but your question rang a bell. In my last project I had pretty much the same problems with another ORM. Instead of letting clients of the business object layer use the ORM generated classes directly or duplicating all classes and implement a ton of forwarding functions, I've defined interfaces.

The clients of your business object layer would only see those interfaces and your Entity classes would implement those interfaces, with the following advantages.

You could add two new entity types that inherit from Account - RegularAccount and FrozenAccount and add your IsFrozen field as a inheritance condition (table per hierarchy).

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.