Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
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
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.
When cleaning my Android solution I get an error at the end of the project:
========== Clean: 9 succeeded, 0 failed, 4 skipped ==========
Unexpected error - Please file a bug report at http://bugzilla.xamarin.com. Reason: System.IO.FileNotFoundException: Could not load assembly 'TheAA.DS.App.Core.Android, Version=, Culture=neutral, PublicKeyToken='. Perhaps it doesn't exist in the Mono for Android profile?
The assembly in question is one of the class library projects in the solution that was cleaned, so I wouldn't expect that assembly to load as it would have (correctly) been deleted by the cleaning process.
Can you please provide
Can you please provide your environment information?
Help - About Microsoft Visual Studio - Copy Info.
Also, is what's the structure of your solution? Is there any custom build actions in your project?
Can you please attach a Diagnostic build output for the Clean, which can help us to understand what's going on in this case?
You can go to "Tools - Projects and Solutions - Build and Run - MSBuild project build output verbosity" and set it to "Diagnostic".
Then Clean the project/solution, and share us the content of the Build Output Window.
As we've added several improvements to our build system and deploying/debugging mechanism since the bug was reported, and we couldn't reproduce the issue at our end, I'm resolving it tentatively as Not_Reproducible.
That said, if you're still facing this issue with current bits, please feel free to reopen the bug and provide the requested information.