title: What is the simplest way to convert a WCF Data Services OData provider to Web API?
body: <p>I'm currently looking at the feasibility of converting our current WCF Data Services OData provider to Web API OData.</p>
  
  <p>I'm just a little confused at the OData implementation for Web API. With WCF Data Services it sits over the top of our ADO.Net entity model which exposes a bunch of tables from the SQL Server backend, i.e. you give WCFDS the ADO model to generate and then you have access to all of the tables through the standard OData syntax.</p>
  
  <p>With Web API from all reading so far do we create a controller or separate actions for every table/object that we want to expose? Am I missing something? Is there just a way where the OData Web API controller can just expose the entire model from the ADO Data model? Having to create a action for every table would be a mess and overkill.</p>
  
  <p>Currently if we need to add a table we just map it in the EDMX and WCFDS will automatically expose it as it's mapped to the entire context of the model.</p>