Entity Framework is both a nice ORM and a confusing one, by default you get features that work well within a context scope, but outside (I.e. disconnected) it doesn’t work nicely. For example exceptions get thrown or navigation properties are emptied.
For work I wrote my own repository classes (as a lot of people do) that sit on top of Entity Framework and I use it a particular way. I’m more than happy with it and I can mix stored procedures with it when I need to.
I’ve put together some test cases that show some of the problems and some manual ways you can use it differently:
https://github.com/piddle/Piddle.EntityFramework.DisconnectedRepo
Granted, this might not be that useful to anyone other than me, but I don’t know until the gits voice an opinion.
Tim's cycling blog 