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.
See screencast to reproduce at http://screencast.com/t/0kvQhyYI0
When switching from View->Message Bubble->Errors Only to View->Message Bubble->Errors & Warnings (if the document has been unedited), warnings will not get displayed
Sorry meant to add this...
Very good screencast.
Without it I would've closed it. The bug is not the message bubble command, it's in our project/task system.
When building a project the task list is cleared, even if the build doesn't occur (like in a project with warnings). Thats why the warnings won't get displayed.
The BeginBuild (IProgressMonitor monitor) function in ProjectOperations just does a:
if (StartBuild != null)
StartBuild (this, new BuildEventArgs (monitor, true));
The big question is: Is that a bug at all ? I would suggest no, it's not a bug at all. If we "fix" that the task list won't show the result of the last action anymore - the last action in that case is a build (which didn't occur because it has already been build).
But in any case, I've added lluis to this issue, because it's more a project system thing (affects the task list as well).
@lluis: What's your opinion about that ?
This bug has been in the NEEDINFO state with no changes for the last 90 days. Can we put this back into the NEW or CONFIRMED state, or are we still awaiting response?
If there is no change in the status of this bug over the next two weeks, this bug will be marked as NORESPONSE.
This bug has not been changed from the NEEDINFO state since my previous comment, marking as RESOLVED NORESPONSE.
Please feel free to REOPEN this bug at any time if you are still experiencing the issue. Please add the requested information and set the bug back to the NEW (or CONFIRMED) state.