Bug 25309 - error assembly not found
Summary: error assembly not found
Status: RESOLVED DUPLICATE of bug 23210
Alias: None
Product: Android
Classification: Xamarin
Component: MSBuild ()
Version: unspecified
Hardware: PC Windows
: Normal normal
Target Milestone: ---
Assignee: Jonathan Pryor
URL:
Depends on:
Blocks:
 
Reported: 2014-12-11 20:49 UTC by Morris
Modified: 2016-04-29 21:40 UTC (History)
5 users (show)

Tags:
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:
Status:
RESOLVED DUPLICATE of bug 23210

Description Morris 2014-12-11 20:49:31 UTC
Warning	1	Unexpected error - Please file a bug report at http://bugzilla.xamarin.com. Reason: System.IO.FileNotFoundException: Could not load assembly 'HelloXamarinFormsWorld, Version=, Culture=neutral, PublicKeyToken=null'. Perhaps it doesn't exist in the Mono for Android profile?	HelloXamarinFormsWorld.Android
Comment 1 Rolf Bjarne Kvinge [MSFT] 2014-12-15 04:04:51 UTC
Is this an issue with Xamarin.iOS or Xamarin.Android?

In any case, please attach a complete build log (preferrably with a test project).
Comment 2 Brendan Zagaeski (Xamarin Team, assistant) 2016-04-29 21:40:04 UTC
I will mark this as a duplicate of an older bug about this same _warning_.

Note that this message can also appear as an _error_. I have filed a separate bug about improving the wording of the _error_ in Bug 40782.

*** This bug has been marked as a duplicate of bug 23210 ***