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.
1) Compiled monodevelop with --enable-test passed to configure.
2) Build and run any of the unit test assemblies
3) This works perfectly.
4) Open the cecil solution in main/external/cecil
5) Build and attempt to run any of it's tests
It fails with error .
This is caused by our external test runner attempting to load the test assemblies in the same appdomain as itself. These particular test assemblies are compiled against NUnit 18.104.22.16892, which is bundled in cecils source code. We need to be able to support this kind of construct with our test runner. NUnit itself already supports this so we just need to fix our ExternalTestRunner to not require loading these assemblies in its own appdomain. Alternatively we could pull in the NUnit source code and compile it directly into our ExternalTestRunner so that it has no dependency on any external assemblies.
 ERROR [2012-06-22 11:26:00Z]: System.TypeLoadException: Could not load type 'NUnit.Core.Extensibility.IAddinRegistry, nunit.core.interfaces, Version=22.214.171.12492, Culture=neutral, PublicKeyToken=96d09a1eb7f44a77'. at (wrapper xdomain-invoke) MonoDevelop.NUnit.External.NUnitTestRunner:Initialize (string,string,string)
at (wrapper remoting-invoke-with-check) MonoDevelop.NUnit.External.NUnitTestRunner:Initialize (string,string,string)
at MonoDevelop.NUnit.External.ExternalTestRunner.GetRunner (System.String assemblyPath) [0x00060] in /Users/alanmcgovern/Projects/monodevelop/main/src/addins/NUnit/Services/ExternalTestRunner.cs:101
at MonoDevelop.NUnit.External.ExternalTestRunner.Run (IRemoteEventListener listener, ITestFilter filter, System.String path, System.String suiteName, System.Collections.Generic.List`1 supportAssemblies) [0x00000] in /Users/alanmcgovern/Projects/monodevelop/main/src/addins/NUnit/Services/ExternalTestRunner.cs:80
at (wrapper managed-to-native) System.Runtime.Remoting.RemotingServices:InternalExecute (System.Reflection.MethodBase,object,object,object&)
at System.Runtime.Remoting.RemotingServices.InternalExecuteMessage (System.MarshalByRefObject target, IMethodCallMessage reqMsg) [0x000c2] in /private/tmp/monobuild/build/BUILD/mono-2.10.9/mcs/class/corlib/System.Runtime.Remoting/RemotingServices.cs:138
Seems to work in 6.0