Bug 37077 - Build Succeeded and unexpected error
Summary: Build Succeeded and unexpected error
Status: RESOLVED NORESPONSE
Alias: None
Product: Visual Studio Extensions
Classification: Xamarin
Component: Xamarin.Forms ()
Version: unspecified
Hardware: PC Windows
: --- normal
Target Milestone: ---
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2015-12-16 12:34 UTC by Michael
Modified: 2016-12-23 00:07 UTC (History)
4 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 NORESPONSE

Description Michael 2015-12-16 12:34:28 UTC
I need some help with this bug.   In VS 2015 on Windows 10 and I want to deploy to my Android emulator.

I got this error ... after my build succeeded 

Has anyone see this before ?









2>Task Performance Summary:
2>        0 ms  Message                                    2 calls
2>        0 ms  MakeDir                                    1 calls
2>        0 ms  AssignProjectConfiguration                 1 calls
2>        1 ms  WriteLinesToFile                           1 calls
2>        1 ms  FindUnderPath                              2 calls
2>        1 ms  RemoveDuplicates                           1 calls
2>       18 ms  ReadLinesFromFile                          1 calls
2>       33 ms  Delete                                     4 calls
2>
2>Build succeeded.
2>
2>Time Elapsed 00:00:00.05
========== Clean: 2 succeeded, 0 failed, 0 skipped ==========
Project "Frienedy.Droid.csproj" (UpdateAndroidResources target(s)):
Project "Frienedy.csproj" (GetTargetPath target(s)):
All projects referencing Frienedy.csproj must install nuget package Microsoft.Bcl.Build. For more information, see http://go.microsoft.com/fwlink/?LinkID=317569.
Done building project "Frienedy.csproj".
Unexpected error - Please file a bug report at http://bugzilla.xamarin.com. Reason: System.IO.FileNotFoundException: Could not load assembly 'Frienedy, Version=, Culture=neutral, PublicKeyToken='. Perhaps it doesn't exist in the Mono for Android profile?
Done building project "Frienedy.Droid.csproj" -- FAILED.

Project "Frienedy.Droid.csproj" (UpdateAndroidResources target(s)):
Project "Frienedy.csproj" (GetTargetPath target(s)):
All projects referencing Frienedy.csproj must install nuget package Microsoft.Bcl.Build. For more information, see http://go.microsoft.com/fwlink/?LinkID=317569.
Done building project "Frienedy.csproj".
Unexpected error - Please file a bug report at http://bugzilla.xamarin.com. Reason: System.IO.FileNotFoundException: Could not load assembly 'Frienedy, Version=, Culture=neutral, PublicKeyToken='. Perhaps it doesn't exist in the Mono for Android profile?
Done building project "Frienedy.Droid.csproj" -- FAILED.
Comment 1 Jose Gallardo 2016-05-18 13:59:06 UTC
Hi Michael,

Can you please provide the environment information?

Help - About Microsoft Visual Studio - Copy Info


Also, it would be great if you can share a diagnostic build output.

Go to "Tools - Options - Projects and Solutions - Build and Run - MS Build project build output verbosity" and set it to "Diagnostic".

Then please build the project and share with us the build output window content.

Thanks!
Comment 2 Jose Gallardo 2016-12-23 00:07:48 UTC
Hi,
I'm resolving this bug as "No Response".
That said, if you're still facing this issue with current bits, please feel free to reopen the bug and provide the requested information.

Thanks