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.
New in MfA 4.1 is delay-signed assemblies. These make it very hard to run unit tests that need to link to these assemblies.
"\Program Files (x86)\Mono-2.10\bin\sn" -vf "C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\MonoAndroid\v2.1\OpenTK.dll"
Mono StrongName - version 18.104.22.168
StrongName utility for signing assemblies
Copyright 2002, 2003 Motus Technologies. Copyright 2004-2008 Novell. BSD licensed.
Assembly C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\MonoAndroid\v2.1\OpenTK.dll is delay-signed but not strongnamed
jonp says on IRC: <@jonp> fak: as for Mono.Android.dll, looks like we're delay signing, then never signing. :-/
It would be great to get these things fully signed in the next MfA release so the unit testing can continue!
Strong Name verification can be disabled using sn -Vr
Fixed for 2.0