You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This seems like a pretty fundamental feature. Shouldn't it be highlighted somewhere more prominent?
In my case, I was able to set MONO_ENV_OPTIONS="--debug" so I can get filenames and line numbers when running tests under mono using dotnet test (when the test project targets .NET Framework and runs on Linux/macOS).
I found mono --debug in the debugging docs, but couldn't figure out how to get it passed through with dotnet test until I found MONO_ENV_OPTIONS.
The text was updated successfully, but these errors were encountered:
@akoeplinger I wonder if we can format the mono manpage and put it somewhere useful either on the mono website, or in the .NET docs.
Googling around, the online copies of the manpage are usually pretty out of date, and folks using modern .NET 6+ Mono don't install the MDK, so the manpage isn't available locally.
I stumbled across
MONO_ENV_OPTIONS
in the 2.8 release notes. I also see it mentioned once in the LLVM docs page, but nowhere else.This seems like a pretty fundamental feature. Shouldn't it be highlighted somewhere more prominent?
In my case, I was able to set
MONO_ENV_OPTIONS="--debug"
so I can get filenames and line numbers when running tests under mono usingdotnet test
(when the test project targets .NET Framework and runs on Linux/macOS).I found
mono --debug
in the debugging docs, but couldn't figure out how to get it passed through withdotnet test
until I foundMONO_ENV_OPTIONS
.The text was updated successfully, but these errors were encountered: