This blog has been a little quiet for a while now.

With good reason though.

I've been doing the hard yards answering questions on the Entity Framework forum.

To do so I had to ask literally hundreds of questions of the rest of the Entity Framework team. Guys like Colin must be completely sick of me barging into their office by now!

Now because the Entity Framework is a complicated thing, it seems no one person understands it 100%, so while answering questions I've been consciously working on building a kind of mental model to help me understand the Entity Framework.

So aside from the obvious benefit of actually answering forum customer's questions, this exercise has been hugely beneficial for me.

I have learnt a lot about two key things: the Entity Framework itself and more importantly the problems Customers are really having with the Entity Framework.

Those two things have lead to a renewed sense of purpose for this Blog.

<Intent>
I'm going to start creating 'real world' applications using the Entity Framework, and I'm going to blog about all the tradeoffs I make, the hoops I have to jump through, the gotcha's I encounter, the workarounds, the design considerations etc.

So what do I mean when I say 'real world'?

Well I mean applications that you might actually find useful or can relate to: apps with multiple tiers, with a little SOA thrown in, maybe a pinch of mid-tier caching, some data-binding, serialization, validation, auditing, work-flows, thin clients, batch processing, queuing, maybe a bit of WPF, WCF, Biztalk, Office and Sharepoint integration. Basically whatever helps to get the job done.
</Intent>

All I need to get me started, is a real world application. Now while I have lots of ideas, I really want to hear from you.

Anyone have any ideas?