This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 55.00000000000001%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESR%3C/text%3E%3C/svg%3E)
How can I get rid of messages like the one below that appear in the VS Community 2022 Output window while debugging? While trying to fix some other problem the other day, I must have changed something that triggered them, but I can't recall what might have done that. I've tried setting/unsetting a number of options in Debug => Options => Debugging => General and Output Window, but so far no luck.
dbug: Microsoft.AspNetCore.Components.RenderTree.Renderer[3] Rendering component 15 of type Microsoft.AspNetCore.Components.Forms.InputFile
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(256, 32%, 34%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMT%3C/text%3E%3C/svg%3E)
These messages are live messages coming from the ASPNET runtime while it runs. The specific message you posted is a debug logging message from the framework.
These messages are controlled by your app's appsettings file. Go to your app's appsettings.json (and/or appsettings.development.json). Then find the logging section. Within there are various "namespaces" and what logging level they are at. You probably have one of the logging levels set to Debug which is showing you a lot more information. By default Microsoft is generally set to Information and others can be set how you want. Change the logging level to Information for most or a higher level, as you like.
Refer to this article on logging in ASP.NET Core for more information on logging levels and how to control them.
This prompted me to find the answer. I had added the code below to Program.cs based on something I saw from CoPilot. Once I removed that statement, the extra messages disappeared. Thanks Michael.
builder.Logging.SetMinimumLevel(LogLevel.Debug);