Bug 12515 - GetAssemblies doesn't return assemblies
Summary: GetAssemblies doesn't return assemblies
Alias: None
Product: Android
Classification: Xamarin
Component: Mono runtime / AOT Compiler ()
Version: 4.6.x
Hardware: PC Windows
: High normal
Target Milestone: ---
Assignee: Bugzilla
Depends on:
Reported: 2013-06-03 03:41 UTC by Neil Boyd
Modified: 2017-04-28 20:03 UTC (History)
4 users (show)

Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and 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 Links.

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 for Bug 12515 on Developer Community or GitHub if you have new information to add and do not yet see a matching new report.

If the latest results still closely match this report, you can use the original description:

  • Export the original title and description: Developer Community HTML or GitHub Markdown
  • Copy the title and description into the new report. Adjust them to be up-to-date if needed.
  • Add your new information.

In special cases on GitHub you might also want the comments: GitHub Markdown with public comments

Related Links:

Description Neil Boyd 2013-06-03 03:41:12 UTC
Calling AppDomain.CurrentDomain.GetAssemblies() in a second app domain in a release build doesn't return the list of assemblies.

See forum post for more information and a sample project that demonstrates the issue.

This is blocking for us because we are enable to upgrade Xamarin.Android beyond 4.6.00049.  It definitely occurs in 4.6.06000, and a colleague of mine tried all versions after 4.6.00049.
Comment 1 Neil Boyd 2013-06-04 03:22:14 UTC
I also confirmed that this bug exists in 4.6.08007
Comment 2 Neil Boyd 2013-08-06 03:57:17 UTC
Is this bug going to be fixed any time soon, or should I implement a workaround?
Comment 3 Rodrigo Kumpera 2013-08-09 10:53:29 UTC

Can you take a look at this one?

Comment 4 Neil Boyd 2014-09-16 03:13:37 UTC
In case it wasn't obvious by now, we implemented a workaround ;)