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 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.
If a solution contains projects which will not work on the current machine/architecture/etc or which contain errors preventing their compilation, attempting to run current or startup project will result in a failure. The only way to run such a project is to select it in the solution pad and run it from its context menu there. Running the project should cause recompilation only of the project itself and all of its changed dependencies.
I agree. There is also a performance issue here. I do not want non-dependent projects compiled when they do not need to be.
Fixed in master.
With the latest builds:
This issue does not exists, as when we run a project from the solution pad from
its context menu there, the project causes recompilation only of the project itself and all of its changed dependencies.
Hence, closing this issue.