Have you considered porting Aforge to .NET Standard?

[JerryNixon]

There is currently a .NET Framework dependency.
Writing for the cloud makes this dependency a bummer.
For example, serverless functions don't easily support this.

Simple question, and just wondering/curious, any plans for a .NET Standard version?

Thank you.

[andrew.kirillov]

Did not have a plan for this. Although never say never, currently I can not see how to get time for this as the project lacks support and was done at spare time in the past.

[JerryNixon]

I get it. I work on a few open source projects, too. It's a mix of exciting and annoying sometimes. You feel like you are building something great on one hand. You feel like you have a real life, too, on the other. Thank you for the help you have provided so far.

A C# library of some of the core capabilities of OpenCV is a real gap in the world right now. And, to be honest, without .NET Standard, anything else doesn't have much of a cloud story. I think the cloud will start to wean out some libraries in a few years making certain others, regardless of their capabilities, only based on their compatibilities, emerge as libraries of choice.

There is real overhead right now to include OpenCV in anything. There is basically zero overhead for .NET Core (which complies with .NET Standard). Aforge today has its own overhead of .NET Framework. This works great for local solutions and windows server solutions, but .NET Framework support in the cloud (by which I mean Azure) is waning fast. A .NET Standard Aforge would be a welcome tool. And, yet, I understand the contraints of real life. Thanks for the note.