Thanks for mention this issue with SharpGL. Maybe this explains the behaviour I see at present. I am using 2.0 and according to the link you provided version 2.1 should be fine without this error.
I switched to SharpGL for two reasons:
1) At many places on the net I have read that openTK is dead.
2) The naming of the functions in SharpGL looks for me more like the standard C functions, so discussing the features seems to be easier.
I switched to SharpGL for two reasons:
1) At many places on the net I have read that openTK is dead.
2) The naming of the functions in SharpGL looks for me more like the standard C functions, so discussing the features seems to be easier.