Bug 9965 - Running multiple MonoDevelop, compiling MonoDroid app, gets the error: "MSBuild operation failed"
Summary: Running multiple MonoDevelop, compiling MonoDroid app, gets the error: "MSBui...
Alias: None
Product: Android
Classification: Xamarin
Component: MSBuild ()
Version: 4.8.x
Hardware: PC Mac OS
: Normal normal
Target Milestone: ---
Assignee: Bugzilla
Depends on:
Reported: 2013-01-31 21:36 UTC by dj_technohead
Modified: 2013-12-05 18:33 UTC (History)
2 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 or GitHub 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 dj_technohead 2013-01-31 21:36:12 UTC

Comment 1 dj_technohead 2013-01-31 21:37:05 UTC
When running multiple copies of MonoDevelop simultaneously, when trying to compile a MonoDroid project, it will result in the error: "MSBuild operation failed".
Comment 2 Atsushi Eno 2013-05-22 14:49:15 UTC
Could you give us example reproducible solution? Also the actual build output would be great to have. There might be the actual reason of errors in the output. Thanks!
Comment 3 PJ 2013-11-19 17:03:57 UTC
This bug has been in the NEEDINFO state with no changes for the last 90 days. Can we put this back into the NEW or CONFIRMED state, or are we still awaiting response?

If there is no change in the status of this bug over the next two weeks, this bug will be marked as NORESPONSE.
Comment 4 PJ 2013-12-05 18:33:58 UTC
This bug has not been changed from the NEEDINFO state since my previous comment, marking as RESOLVED NORESPONSE.

Please feel free to REOPEN this bug at any time if you are still experiencing the issue. Please add the requested information and set the bug back to the NEW (or CONFIRMED) state.