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
GitHub or Developer Community 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.
If you use Nancy  webframework and are a firm believer of unit testing, it's very probable that you end up using Nancy.Testing  library, which embeds the TinyIoC  container.
This works well in Mono.
However, if, for creating stubs/mocks of collaborators in your unit tests, you decide to use any Castle.DynamicProxy  based library, such as Rhino.Mocks , then you have very high chances of running into exceptions like TinyIoCResolutionException when running your tests on Mono (but not MS.NET).
I've tracked this down to a subtle bug in System.Reflection.Emit when emitting dynamic assemblies. Pull request coming in a few minutes, with a fix and a unit test.
PR was merged.
Pulled and fixed an additional issue.
Thanks for the patch.
Thanks for your review & merge & addition!