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.
It should not be possible for the startup project to be a non-executable project, such as a library. This means that run/debug commands become disabled, which is potentially confusing.
Of course there are subtleties, e.g.:
* A project might be executable but might not be able to run for some other reason. In such cases it's probably better to allow running the commands, then show an error, instead of disabling the command.
* Library projects can become executable when they have a custom execution command, that can for example load and run the library using some executable.
* Projects may be added or removed, or may have custom commands added, or have their output type changed. MD would have to track this.
But MD should have a better default for the startup project when it can. Ideally, the run/debug commands would become disabled only when there is no executable project in the solution.
This is already fixed.