Bug 39793 - System.IO.FileNotFoundException: Could not load assembly
Summary: System.IO.FileNotFoundException: Could not load assembly
Status: RESOLVED DUPLICATE of bug 40782
Alias: None
Product: Visual Studio Extensions
Classification: Xamarin
Component: Android ()
Version: unspecified
Hardware: PC Windows
: --- normal
Target Milestone: ---
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2016-03-20 18:42 UTC by ganeshparikh
Modified: 2016-08-03 15:24 UTC (History)
6 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 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 40782

Description ganeshparikh 2016-03-20 18:42:46 UTC
Unexpected error - Please file a bug report at http://bugzilla.xamarin.com. 
Reason: System.IO.FileNotFoundException: Could not load assembly 'App3, Version=, 
Culture=neutral, PublicKeyToken='. 
Perhaps it doesn't exist in the Mono for Android profile?
Comment 1 Brendan Zagaeski (Xamarin Team, assistant) 2016-04-29 19:43:55 UTC
I will mark this as a duplicate of a new bug I have filed to request that Xamarin.Android should emit the same standard error message as other C# apps for this scenario.

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