4 ms·
I took a quick glance of your github codebase, I must say that you are reinventing wheels: for the purpose of Entity Modeling, you can use Entity Framework dire
by henryliang 6y ago
I took a quick glance of your github codebase, I must say that you are reinventing wheels: for the purpose of Entity Modeling, you can use Entity Framework directly, or similar packages (Dapper, NHibernate...)
For general common purpose library, you may refer to a really old library called Enterprise Library for standard .net framework. It provides a lot of common functionalities that can inspire you for build your library in .net core, or you may find someone else have already done one.
BTW, this is my first comment ever. I used to programming in C# and .net for 10+ years but for the past 5 years I switch to javascript/typescript on Node.js and python.
- controlledchaos 6y agoThanks 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 agoYou 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 agoThat 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.