Hello,
I am new to WebApi development and ASP.NET in overall and wondering if I should start new products building with ASP.NET Data Entity model. I mean, I would like to follow a Database First approach when I develop REST apis with .net (also I would use stored procedures for complicated/batch inserting and views when there is a need to display complex query results). To achieve this, I tried this approach:
- Made a WebApi, MVC (.net 4.7) project
- Added an ADO.NET Data Entity Model
- Generated controllers using visual studio's scaffolding -> Web API 2 Controller with actions, using Entity Framework
- Each controller can be customized, but mostly is working (only tried tables so far)
Is this approach sustainable long term (for a quite big, business application's backend)? I also tried and could successfully add OData support to one of the controllers and would like to use it to quickly create pageable/sortable/filterable endpoints for the UI tables.
(I am asking this question, because both OData and ADO.NET Data Entity Model seems quite ignored by the community - I mean, mostly on stackoverflow, and I do not want to start working with something that is abandoned by most people.)