Conversation
Though token+offset is useful for certain scenarios, they might not be usable for majority of scenarios. So disabling them by default.
|
Incidentally, I wanted to see how I'd set this flag without editing the code. I got to here and it says it's either registry or @eerhardt is that right? |
That doc looks like it hasn't been updated for .NET Core/5+. Nothing in the runtime respects app.config files, and I'm pretty sure we don't look in the registry anymore either. |
|
Assume we need a separate issue to fix the doc issue? |
…ger_proxy_attribute * origin/main: disable token info in traces. (dotnet#56780) [debugger] Fix debugger.break behavior (dotnet#56788) [mono][wasm] Allow setting env variables with '=' characters in the test runner. (dotnet#56802) Ecma edit for `conv.ovf.<to type>.un`. (dotnet#56450) Mark HandleProcessCorruptedStateExceptionsAttribute as obsolete (dotnet#56664) Enable SxS install of previews on Mac OS (dotnet#56797) CoreCLR runtime tests + Mono on the x64 iOS simulator (dotnet#43954) [main] Update dependencies from mono/linker (dotnet#56593) STJ: Fix deserialization of UInt16 properties (dotnet#56793)
Yeah, here is a random example of another issue tracking adding docs if it helps. dotnet/diagnostics#1347 |
Though token+offset is useful for certain scenarios, they might not be usable for majority of scenarios. So disabling them by default. It was enabled by default in #44013