Seconded. A general idea when you plan a final release would be welcome. I am stuck in EF5 hell with some elements (mostly the inability to properly work with an open connection that locks the objects edited - not for long, it is a "load, update, save while noone else does it" thing that just is faster than the retries in a system that gets a lot of updates (say: account totals). Would love to rip out some stored procedures.... but that really needs EF6.
↧