Bug 2590 - MonoDevelop hides errors when launching xsp web server
Summary: MonoDevelop hides errors when launching xsp web server
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: ASP.Net ()
Hardware: Macintosh Mac OS
: Normal normal
Target Milestone: ---
Assignee: Bugzilla
Depends on:
Reported: 2011-12-20 20:07 UTC by Mike Christensen
Modified: 2015-09-18 10:26 UTC (History)
3 users (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 for Bug 2590 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 original description:

  • Export the original title and description: Developer Community HTML or GitHub Markdown
  • Copy the title and description into the new report. Adjust them to be up-to-date if needed.
  • Add your new information.

In special cases on GitHub you might also want the comments: GitHub Markdown with public comments

Related Links:

Description Mike Christensen 2011-12-20 20:07:53 UTC
When launching xsp, MonoDevelop can potentially hide useful errors messages when web server starts.

To repro:

1) Start MonoDevelop on Mac using non-root user.
2) Create default web project
3) Configure xsp to use port 80 (Not allowed when not running as root)
4) Run


Project will build, the debugging environment will quickly flash on the screen and then go away.  Nothing useful is prevented to the user.

However, if the user goes to the "Application Output" tab, they'll see an error message such as:

Listening on address:
Root directory: /Users/mike/KitchenPC/KPCServer
Error: System.Net.Sockets.SocketException: Access denied
  at System.Net.Sockets.Socket.Bind (System.Net.EndPoint local_end) [0x00000] in <filename unknown>:0 
  at Mono.WebServer.XSPWebSource.CreateSocket () [0x00000] in <filename unknown>:0 
  at Mono.WebServer.ApplicationServer.Start (Boolean bgThread) [0x00000] in <filename unknown>:0 
  at Mono.WebServer.ApplicationServer.Start (Boolean bgThread, System.Exception initialException) [0x00000] in <filename unknown>:0 
  at (wrapper remoting-invoke-with-check) Mono.WebServer.ApplicationServer:Start (bool,System.Exception)
  at Mono.WebServer.XSP.Server.RealMain (System.String[] args, Boolean root, IApplicationHost ext_apphost, Boolean quiet) [0x00000] in <filename unknown>:0 

Note: If "Run on External Console" is selected, there will be no way to see this error at all.


MonoDevelop should trap error results when launching web server and display some sort of helpful error message on the screen as to why the application could not start.