Bug 4268 - Startup project should not be able to be a non-executable project
Summary: Startup project should not be able to be a non-executable project
Status: RESOLVED FIXED
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: Project Model ()
Version: Trunk
Hardware: PC Mac OS
: Normal normal
Target Milestone: ---
Assignee: Lluis Sanchez
URL:
Depends on:
Blocks:
 
Reported: 2012-04-05 12:41 UTC by Mikayla Hutchinson [MSFT]
Modified: 2015-07-02 10:40 UTC (History)
1 user (show)

Tags:
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:
Status:
RESOLVED FIXED

Description Mikayla Hutchinson [MSFT] 2012-04-05 12:41:33 UTC
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.
Comment 1 Lluis Sanchez 2015-07-02 10:40:27 UTC
This is already fixed.