Join Project With AArnott/pinvoke? about vanara HOT 4 CLOSED

This project came out my need for a large PInvoke library. I looked hard at AArnott's project, and even corresponded with him. In the end, I decided to do my own as I was looking for a less purist approach and more of a functionally useful library. I likely will not join that project due to this difference in approaches.

from vanara.

Thanks for your response. I understand your reasons, and checked some more of your code.

But at the end the P/Invoke part is very similar in both projects. Which of course is technical requirement, because the WIN32-API is how it is.

For example: Both librarys provide a P/Invoke for CreateProcess which still let the dev/user handle translation of WIN32 error codes into an exception. I even don't see another small feature layer for that, that would throw a exception if creating a process fails.

I understand that parts like your NetworkConnection classes are not in the scope of Arnott/pinvoke. But the P/Invoke stuff, which is already a lot of very similar work and code and potential conflict and confusion in a app that consumes both.

from vanara.

#6 asks same. And https://github.com/AArnott/pinvoke has almost 6 times more stars. And https://github.com/AArnott/pinvoke is more lower level. At least you could keep #32 open for discussion and voting. I port my PInvokes to that because as I see it suits.

from vanara.

Thanks for this hint @dzmitry-lahoda . Shame on me I have not searched before opening this issue.
At the end it is @dahall project and he has to decided how the direction of his project goes, even we do not agree with that or see it the same way.

from vanara.