I've recently "inherited" a part built project from a developer who as left our company.
He had decided to use Entity Framework but I am finding it to be unstable and slow. I periodically have to reimport objects and stored procedures from the database as the model gets corrupted. I also find database processes to be slower than if I was just running stored procedures and ADO.net
The latest fresh hell it has started to pull is an error New transaction is not allowed because there are other threads running in the session.
I've looked on line and the answer seams to be to do with running updates while reading through data in a loop. Except the code that is throwing the error is not in any loop although it is calling a stored procedure that runs an update.
It could be the Framework or it could be how it has been implemented by my predecessor ( his idea of OOP and N tier left something to be desired,) the issue is it's a big project and I'm not sure the powers that be would be happy if I started again.
So I'm wondering if there is a way to just take the entity part out and build an old fashioned data layer with views and stored procedures... ( and optimised SQL in those proceedures)