Is there a common repository or persistence pattern interface in .NET? -


After text

Net exposes the data as a universal pattern for querying data from various data sources, including data treasure, and Very powerful. The ASP.NET Web API instantly exposes IITAP resources as the GET methods in the form of the OADATA interface. However, I think that every data is access layer layer solution, which includes the entity framework, and displays its own proprietary interface to insert, update and delete data associated with a repository or data source. Therefore when the IQueryable selection / data is analogous to query, IQueryable, create dynamic, or delete the data, when the query is not applicable for the data except as changing the data asked.

DAL out for its own purposes, including the ability to swap, I'm probably going to be a small cover interface library that strengthens CRUD interface of any type. This probably looks like HTTP action action semantics and enjoys IQueryable as the basis of GAT / Read. But before I select this I do not have anything in BCL, and if not so if there is anything used in the heavy community, which already already (beyond the IQueryable) select / beyond the query CRUD interface exists to describe?

(And if not, as a side idea, why not a cat? These 2014 o / rms are no longer sexy [this is not officially part of my question], We are supposed to be this past, but not apparently. My only guess is "for different reasons of maintaining relational integrity or changing the state awareness", bleaching.)


Comments

Popular posts from this blog

ios - How do I use CFArrayRef in Swift? -

eclipse plugin - Run java code error: Workspace is closed -

c - Error on building source code in VC 6 -