I understand that EF is tightly mapped against database. I also understand that we can generate POCO classes replacing EF based classes.
I have the following scenario.
We have a large framework of legacy non-serializable API written in .NET framework 2.0 (and we cannot modify that). We will not have direct access to database and all the operations must go through existing APIs. We wanted to have new layer on top of that API (with some DTOs) providing support to Serialization and IQueryable. The goal is to expose this layer as WCF data services with oData support.
Can EF 4.0 with/without POCO help us on this? If so any good links? If not, any suggestions in moving forward?
thanks