3 ms·

Thanks for replying! To your first point, Dapper is heavily used within this framework. Being able to pass or return models from a query is amazing! My goal w

Thanks for replying! To your first point, Dapper is heavily used within this framework. Being able to pass or return models from a query is amazing! My goal with this was to allow a developer to create their models and be up and running with a RESTful API in hours, without needing to configure each controller route.

henryliang 6y ago
You are very welcome. To your goal of allowing devs to set up a RESTful API quickly without configuring controller route, .net core already provides the web api which allows you to hook up with Entity Framework really quickly. IMHO, that paradigm is a very good balance between "quick startup" and "flexible enough for further development". I suggest you to take this approach and try it out, as comparison to your codebase. Hope this help a bit. :)
- controlledchaos 6y ago
  That looks to be exactly what I need. I had rolled my own solution using Dapper, as Entity Framework scared me off in the past. Seems to have matured a lot since I last used it.