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 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.
As a developer when working in Xamarin Forms, 99% of the time I only want to see debug output from my application and NOT Xamarin. Sifting through massive amounts of Xamarin debug spew is very time wasting.
Can you please provide an option to redirect all Xamarin output to the XAMARIN Output window and NOT the debug output window.
Can you be a bit more specific of the types of logging that are overly verbose? Can you provide an example log that demonstrates certain things a developer might not care to read about?
If these are mono logs, you can potentially try turning down the log level via:
Some logs do get outputted twice, once by the platform and once by mono. I do agree that some logging can be overly verbose, but I wanted to pick your mind to see what logs are time wasting.
Another thought is...Would these logs be better if they had a filtering mechanism built inside Visual Studio? Or would it be better to keep as is with less verbosity?
Thus I am marking this bug as NEEDINFO for the time being.
Thank you for the information, this is exactly what I needed.
Thank you for the assistance.