Apologies if this if not an appropriate use of the issues board. I could find no other way of reaching out to the devs.
TL;DR - Improved documentation could/would aid adoption.
NPoco 6 is an incredible and well crafted library. I only recently discovered it, after spending considerable time looking for a replacement for EF, and I already love working with it.
I encountered resistance from my employers when I proposed adopting NPoco for certain future projects. Their reasoning:
- Lack of active development (the latest release showing here is 5.0, from 2020). I did point out that's not accurate/up to date.
- Documentation is too light, and incomplete.
And I had to accept defeat on the documentation. So much of what NPoco offers simply isn't covered by the documentation. I don't even think I'm using it to its full potential as I'm not aware of what it has to offer. I do believe that with more in-depth and complete documentation, adoption would increase significantly.
Apologies if this if not an appropriate use of the issues board. I could find no other way of reaching out to the devs.
TL;DR - Improved documentation could/would aid adoption.
NPoco 6 is an incredible and well crafted library. I only recently discovered it, after spending considerable time looking for a replacement for EF, and I already love working with it.
I encountered resistance from my employers when I proposed adopting NPoco for certain future projects. Their reasoning:
And I had to accept defeat on the documentation. So much of what NPoco offers simply isn't covered by the documentation. I don't even think I'm using it to its full potential as I'm not aware of what it has to offer. I do believe that with more in-depth and complete documentation, adoption would increase significantly.