3 ms·
I agree with the points raised by another comment here. It appears you are doing a rewrite of Entity Framework. That said, you may have some specific requiremen
by bob1029 6y ago
I agree with the points raised by another comment here. It appears you are doing a rewrite of Entity Framework. That said, you may have some specific requirements that justify this approach. Performance would be the most immediate one that comes to mind if you are planning on some domain-specific optimizations.
Regardless, if you are looking for a good way to build documentation, look no further than DocFX:
https://dotnet.github.io/docfx/index.html https://dotnet.github.io/docfx/index.html
This is something that can be built-in to your CI/CD toolchain and automagically refresh your static HTML docs each time you make changes. All of your actual documentation can live in XML comments above the relevant code members throughout. This is intended to work in concert with the default VS comment style (3 slashes starts XML comment section).
- controlledchaos 6y agoI was hoping to avoid using Entity Framework, but maybe I need to give it another go. This library is more around reducing the amount of code needed to build a RESTful API off of an existing database, so maybe I could use parts of EF. DocFX is exactly what I am looking for. Thanks!