Bug 5239 - MonoDroid library projects should not be settable Startup projects
Summary: MonoDroid library projects should not be settable Startup projects
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: Android Add-in ()
Version: Trunk
Hardware: PC Mac OS
: --- normal
Target Milestone: ---
Assignee: Alan McGovern
Depends on:
Reported: 2012-05-22 11:20 UTC by Alan McGovern
Modified: 2012-05-22 11:22 UTC (History)
1 user (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 Alan McGovern 2012-05-22 11:20:13 UTC
1) Create a Mono for Android application
2) Add a new Mono for Android library
3) Mark the library as the startup project
4) Try to run the solution

MonoDevelop gets confused and throws many different exceptions due to files not existing in the right place (as it's a library and not an Application).
Comment 1 Alan McGovern 2012-05-22 11:22:03 UTC
Fixed in master and 3.0-series