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.
I'm not sure what this is at present, but I'm getting a lot of these exceptions during my VS2010 debug builds - see screenshot at http://imgur.com/W18LZ
Generally these only seem to happen after VS2010 has been open for a while and I've done a few builds.
Hmm, I have never seen that one before, and none of the code listed is any of our code. Will try to come up with a way to track this down.
Looking at this some more I think it's something that VS11 might have changed in the MSBuild installation.
Can you narrow down when exactly it happens?
- Are you triggering just a build (Ctrl-Shift-B)?
- Are you triggering a build and run (F5 or Ctrl-F5)?
If the second, can you tell how far it is getting before you get the message?
There should be some logging in the Output->Build pane.
We've fixed various things that could potentially have caused this, and we've
added better logging so that things shouldn't crash and should give a better
error message for 4.2.2.
If you are still hitting errors in 4.2.2, please file a bug or reopen this one,
hopefully we'll at least provide you with a better error message!
I've got this to happen in 4.2.2 - and I'm afraid the error message still seems the same.
This seems to be occurring maybe four or five times during a 2 minute build (on a fast PC) of a 120 solution project incluing droid, wp7, touch and portable projects - I've not repro'd it in a smaller solution - sorry!
If possible, I'd like to find a workaround for this issue - even if it's just hiding the dialog - before the 22nd June when I'm presenting at an Azure conference - just want to hide the error if possible - otherwise people might not believe how good Mono4Android is :)
*** This bug has been marked as a duplicate of bug 8831 ***