Reenable MSBuild Terminal Logger
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- powershell, shell
- Domain
- build-system, tooling
Research direction
Start with the terminal logger settings in build.sh, build.ps1, and Directory.Build.rsp, then review the reenableTerminalLogger branch and the linked MSBuild change. Try the proposed configuration with detailed verbosity and gather feedback on native build output, test failure results, and project logging before deciding whether to reenable it for 11.0.
Written by the indexing model from the issue text.
Description
We turn off the terminal logger in a few places - the outer build scripts (build.sh/build.ps1) and in Directory.Build.rsp.
Before, we did this because the terminal logger wasn't showing output from native build, nor was it showing test failure results.
The test results issue seems to be fixed, and the native build output can be enabled if we pass in /v:detailed due to https://github.com/dotnet/msbuild/pull/9810.
The largest difference is that logging for a project is not emitted until that project completes, however progress is still shown for the project.
I'd like for a couple folks to try it out and see what they think, if we're happy with it, we can make the change in 11.0.
https://github.com/dotnet/runtime/tree/reenableTerminalLogger
@jkotas @akoeplinger @ViktorHofer @ManickaP
Related https://github.com/dotnet/runtime/issues/94183 https://github.com/dotnet/runtime/issues/97211
- Dominant language
- C#
- Stars
- 18.3k
- Forks
- 5.6k
- PR merge metrics
- PR metrics pending
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from dotnet/runtime
-
agentic-workflows untriaged
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
area-System.Reflection blocking-clean-ci-optional Known Build Error os-mac-os-x untriaged
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
area-CodeGen-coreclr untriaged
Difficulty 1/5 Under an hour Newbie friendliness 92/100
-
agentic-workflows untriaged
Difficulty 1/5 Under an hour Newbie friendliness 78/100
-
area-VM-meta-mono untriaged
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
-
:watch: Not Triaged 11.0 fundamentals/subsvc
Difficulty 2/5 1-3 hours Newbie friendliness 92/100
dotnet/AspNetCore.Docs#37699 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
SubtitleEdit/subtitleedit#15108 · 1 comment ·
-
area/docs-content Bug pulumi/docs
Difficulty 1/5 1-3 hours Newbie friendliness 94/100
-
Create parent directories only after the containment check in InstallHelper.TryExtractToDirectory Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
PowerShell/PSResourceGet#2056 ·