Share via

Output Window Filter - View Tag

Nathan Sokalski 4,126 Reputation points
2021-05-05T21:22:27.737+00:00

I often use Visual Studio 2019's Output Window for debugging my Xamarin.Android apps. However, I nearly always receive tons of unnecessary messages starting with [View], such as the following:

[View] requestLayout() improperly called by androidx.recyclerview.widget.RecyclerView{c1098fc VFED..... ......ID 83,0-1440,94 #7f090150 app:id/rvPlayerNames} during layout: running second layout pass

I have looked at the following to try to figure out how to avoid these messages cluttering the Output Window:

https://learn.microsoft.com/en-us/xamarin/android/deploy-test/environment

But none of the stuff seemed to help. What can I do to restrict the Output Window to (or mostly to) my
System.Diagnostics.Debug.WriteLine
statements? Using these statements is not very useful if they have hundreds of meaningless lines between them.

Visual Studio Debugging
Visual Studio Debugging
Visual Studio: A family of Microsoft suites of integrated development tools for building applications for Windows, the web and mobile devices.Debugging: The act or process of detecting, locating, and correcting logical or syntactical errors in a program or malfunctions in hardware. In hardware contexts, the term troubleshoot is the term more frequently used, especially if the problem is major.
967 questions
0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Tianyu Sun-MSFT 29,446 Reputation points Microsoft Vendor
    2021-05-06T06:23:59.78+00:00

    Hello @Nathan Sokalski ,

    Welcome to Microsoft Q&A forum.

    Please kindly check if these options work for you.

    1). Tools > Options > Xamarin > Android Settings > Xamarin Diagnostics output verbosity.

    2). Tools > Options > Debugging > Output Window > General Output Settings.

    3). Tools > Options > Projects and Solutions > Build And Run > MSBuild project build output verbosity.

    AFAIK, Output Window doesn’t provide more/other options to filter. If above options don’t work, I'm afraid, you may still need to use System.Diagnostics.Debug.WriteLine statements to filter. I recommend you directly suggest this feature to Visual Studio Product Team in Developer Community.

    Best Regards,
    Tianyu

    • If the answer is helpful, please click "Accept Answer" and upvote it.
      Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
    0 comments