Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
Mono organizations on
GitHub to continue tracking issues. Bugzilla will remain
available for reference in read-only mode. We will continue to work
on open Bugzilla bugs, copy them to the new locations
as needed for follow-up, and add the new items under Related
Our sincere thanks to everyone who has contributed on this bug
tracker over the years. Thanks also for your understanding as we
make these adjustments and improvements for the future.
Please create a new report on
Developer Community or GitHub with
your current version information, steps to reproduce, and relevant error
messages or log files if you are hitting an issue that looks similar to
this resolved bug and you do not yet see a matching new report.
Two versions of the OpenTK library are included for Android: C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\MonoAndroid\v4.0.3\OpenTK.dll and OpenTK-1.0.dll in the same folder. The OpenTK-1.0.dll version does not work. For example if you create an OpenGL project it will include the OpenTK.dll version in the references. This will work correctly. If you change the reference to the other version then the app still runs, but the colored square of the demo project will not show up on the screen.
I don't know what'd different between these two versions of OpenTK, but it is confusing to have both, and if the second is truly not useful then it's a waste of space. There are also library incompatibilities between them. Some of the functions require slightly different parameters, etc.
What's also annoying is that both of these versions of OpenTK are not directly compatible with the OpenTK that's included for iOS.
Two different versions of OpenTK.dll are provided to not break compatibility for existing users. Removing one breaks their application. If you alter the dll from the one that the sample references, it would break behavior and not supported.
Incompatibility between iOS and Android is recorded on bug #7384, so we are not going to address it on this specific entry.
(Reassigning to rodo for any possible further messages.)