Bug 36824 - Building Solution fails with error Metadata file '.dll' could not be found
Summary: Building Solution fails with error Metadata file '.dll' could not be found
Alias: None
Product: Visual Studio Extensions
Classification: Xamarin
Component: General ()
Version: 4.0.0 (C6)
Hardware: PC Windows
: --- normal
Target Milestone: ---
Assignee: Bugzilla
Depends on:
Reported: 2015-12-10 12:56 UTC by Matthias Fasching
Modified: 2016-12-22 23:22 UTC (History)
5 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 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 Matthias Fasching 2015-12-10 12:56:27 UTC

with the update yesterday the occasional freezing of Visual Studio seems to have been fixed for me, but now I get a different error. Sometimes (especially after a larger merge of branches) I cannot build a Xamarin solution because I get errors like 

Metadata file '***.dll' could not be found

The only fix appears to be to delete the .suo file associated with the solution and restarting Visual Studio.
Comment 1 Enzo Heredia 2016-04-11 16:16:03 UTC
Are you still seeing this behaviour with our latest Alpha build?
Comment 2 Jose Gallardo 2016-12-22 23:22:29 UTC
As we've added several improvements to our build system and deploying/debugging mechanism since the bug was reported, I'm resolving it tentatively as Fixed.
That said, if you're still facing this issue with current bits, please feel free to reopen the bug.