Bug 53369 - Unable to disable or dramatically reduce Xamarin messages in Output Windows
Summary: Unable to disable or dramatically reduce Xamarin messages in Output Windows
Status: RESOLVED ANSWERED
Alias: None
Product: Visual Studio Extensions
Classification: Xamarin
Component: General ()
Version: 4.3.0 (C9)
Hardware: PC Windows
: --- enhancement
Target Milestone: Future Cycle
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2017-03-15 17:54 UTC by Karl Shifflett
Modified: 2017-07-08 19:11 UTC (History)
5 users (show)

Tags:
Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and 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 Links.

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.

Related Links:
Status:
RESOLVED ANSWERED

Description Karl Shifflett 2017-03-15 17:54:54 UTC
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.

Thank you,

Karl
Comment 1 Jon Douglas [MSFT] 2017-07-07 18:21:39 UTC
Hi Karl,

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:

MONO_LOG_LEVEL

and

MONO_LOG_MASK

http://www.mono-project.com/docs/advanced/runtime/logging-runtime-events/

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.
Comment 2 Karl Shifflett 2017-07-08 19:11:17 UTC
Jon,

Thank you for the information, this is exactly what I needed.

Best,

Karl
Comment 3 Karl Shifflett 2017-07-08 19:11:44 UTC
Thank you for the assistance.