Bug 30652 - Error 36 Unexpected error Reason: System.IO.FileNotFoundException: Could not load assembly 'choices, Version=, Culture=neutral, PublicKeyToken='. Perhaps it doesn't exist in the Mono for Android profile?
Summary: Error 36 Unexpected error Reason: System.IO.FileNotFoundException: Could not ...
Alias: None
Product: Android
Classification: Xamarin
Component: MSBuild ()
Version: 5.0
Hardware: PC Windows
: Normal normal
Target Milestone: ---
Assignee: dean.ellis
Depends on:
Reported: 2015-06-01 22:33 UTC by Mike
Modified: 2017-09-14 19:14 UTC (History)
3 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 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.

Related Links:

Description Mike 2015-06-01 22:33:09 UTC
I have a PCL project that a custom control is referencing in a form from an Android project.  My xaml is not finding my assembly, even though it is using the correct assembly name and namespace.

Just in case this could help- I previously renamed my assembly through the UI over 2 months ago, but I just want to mention it in case - I still have directories that are named with the old assembly name, but everything was working fine until I tried to create a variable in xaml and reference it within the code-behind file (could not find my assembly).  I know that this bug is ongoing, so I hope this helps.
Comment 1 Jonathan Pryor 2015-06-04 15:20:16 UTC
Could you please attach diagnostic build output for when you encounter the error?

Normally this error suggests something wrong in the project itself, e.g. assembly A.dll depends on assembly B.dll, but B.dll cannot be found, for which the solution is to add an assembly reference for B.dll to the main App project.

However, this is the fourth similar bug that has been filed in the last two months, so I'm wondering if something else is going on.

At minimum, we should work on revising this error message.
Comment 2 Sunil Kumar 2015-07-07 06:20:16 UTC
As per comment 1, changing its status as "NEEDINFO".
Comment 3 Jon Douglas [MSFT] 2017-09-14 19:14:25 UTC
Because we have not received a reply to our request for more information we are closing this issue. If you are still encountering this issue, please reopen the ticket with the requested information. Thanks!