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 1186 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
It woud be nice to have an extension point for "build fixes". These would key from the project type and build error codes, and would help to fix the error when possible.
For example, the "you need to specify the /unsafe flag" C# error could have a fix helpers that that would set the flag on the project. The "are you missing a reference" error could have a helper that would open the "edit references" dialog.
that's possible with code actions & code issues.
Not bound to build errors - but a semantic check needs to be done anyways (the information code from the build error is not helping that much)
There are more complex errors possible, e.g. from mtouch in iOS projects. It's not all about C# :)
then they can add to the context issues as well - the system can access anything from MD.
Then they need to be placed in monodevelop/ios addin.
You're missing the point completely...
Some errors simply will not be displayed in the source editor, as they have no location. Or they will be produced by complex logic we can't reproduce, e.g. the linker. For such errors, I would like fixes **in the error list**.
Then make it as trello item - that makes more sense.
From the original description the code issues would fit perfectly.
We weren't using trello when I opened this :)
BTW not all C# error/warnings have location info either
Marek: Doesn't really matter - as far as I understand mhutch wants to link them to the errors - that could be part of the error list for example.