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 46580 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
Created attachment 18380 [details]
Screenshot showing intentionally added typo and resulting dialogs
When a runtime error is encountered in a solution, it displays an error and its position. However, there is no means to navigate to the location of the error. The user must manually open the file and location the position of the source of the error. It should allow a double-click, a link, something that would open the file and place the cursor on the location of the error. I mean, it knows the position so it should be able to navigate there.