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 for Bug 40741 on
Developer Community or GitHub if you have new
information to add and do not yet see a matching new report.
If the latest results still closely match this report, you can use the
In special cases on GitHub you might also want the comments:
GitHub Markdown with public comments
# Steps to reproduce
1. In the Solution properties (in a solution with multiple web applications configured to run on different ports), go the to Run menu on the left, and select the multiple web projects to start instead of just one.
2. Run the solution
3. Notice only one of the web servers start, with Xamarin Studio reporting an error after stopping running of "Could not launch web server. A debugger session is already started." This also happens in release mode.
# Expected behavior
Multiple web servers listening on different ports should all be able to start.
# Actual behavior
Only one server starts.
# Supplemental info (logs, images, videos)
# Test environment (full version information)
Tested on latest alpha and latest stable as of Apr 27 2016.