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.
In between Mono 2.10 and Mono 2.11, the location for xsp.exe for the 4.0 profile changed from $MONO_ROOT/lib/mono/4.0/xsp4.exe to $MONO_ROOT/lib/mono/4.5/xsp4.exe.
MonoDevelop isn't tracking this, so debugging ASP.NET applications doesn't work with any Mono 2.11 version.
Steps to reproduce:
1) Install Mono 2.11.
2) Run MonoDevelop
3) Create a default ASP.NET (MVC) application
4) Try to start the debugger
1) Debugger starts
1) xsp/debugger do not start.
The change that broke this is https://github.com/mono/xsp/commit/d3e2f80ff59ddff68e757a520655555e2fbf2695.
*** Bug 5030 has been marked as a duplicate of this bug. ***
This was fixed in https://github.com/mono/monodevelop/commit/ebbfc32eae4fec27047388d20bbc5b5839bf9cb9. It uses the 4.5 profile dir if it exists, otherwise it uses the 4.0 profile directory.