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.
We have quite a big solution with something about 15 projects in it. It consists of some core libraries and multiple executables using those libs. When I'm starting the required executable using "Run -> Start Without Debugging" all projects in solution are being built. This means that if I made some changes to a core library and want just to check a single executable, all the other executables are built too. On the other hand, if I start the executable via its context menu's "Run Item" the behaviour is different. It builds only selected executable and the required libraries, skipping all the other executables.
I would use this "Run Item" action all the time but there's another problem. I've added key binding to it but it appears then MD runs the project currently selected in the Solution pad but not the one marked as a startup project.
I don't know what the designed behaviour is but it would be great if there was possibility to run startup project and build only projects required by it and not all the others. In Visual Studio this option is called "Only build startup projects and dependencies on Run".
Fixed. Only the dependencies of the startup projects are built now.