Changing "WPF Trace Settings" for Visual Studio debugging has no effect
- Dominant language
- C#
- Stars
- 7.7k
- Forks
- 1.3k
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 61
Description
* .NET Core Version: 3.1.0-preview1.19476.43
* Windows version: Win10 1903
* Does the bug reproduce also in WPF for .NET Framework 4.8?: No
* Is this bug related specifically to tooling in Visual Studio (e.g. XAML Designer, Code editing, etc...)? Yes but I think it's a bug in NetCore
**Problem description:**
Visual Studio has the dialog "Options | Debugging | Output Window" to change the trace level of certain WPF traces. You can turn off traces, or increase the level of traces per WPF feature. Changing the trace output level has no effect in NetCore, the default trace level is always chosen. For example, Data Binding traces will only ever output errors, which is the default.

**Minimal repro:**
* Unzip the following project:
[TestBindings.zip](https://github.com/dotnet/wpf/files/3663736/TestBindings.zip)
* In Visual Studio 16.3.1, open the TestBindingsNetCore.sln solution
* In Tools | Options | Debugging | Output Window | Data Binding, change the setting to "All" or "Off"
* Build and run the project in the debugger (F5), which will have many Binding errors
**Actual behavior:**
Binding errors are shown in the output window
**Expected behavior:**
* If you set the output setting to "All" there should be many more Information items in the output window
* If you set the output setting to "Off" there shouldn't be anything in the output window
Try again with the project TestBindingsNetFx.sln and the setting will work fine (.NET Framework's WPF)
Contributor guide
Assessment
This issue has not been assessed yet.