Notiz
Zougrëff op dës Säit erfuerdert Autorisatioun. Dir kënnt probéieren, Iech unzemellen oder Verzeechnesser ze änneren.
Zougrëff op dës Säit erfuerdert Autorisatioun. Dir kënnt probéieren, Verzeechnesser ze änneren.
Starting in .NET 10, dotnet watch emits its internal-facing log messages to the stderr channel instead of stdout. This change is part of a general trend towards dotnet CLI commands not obscuring the stdout channel. That channel is often reserved for special semantics when running certain kinds of applications, like LSP or MCP servers.
Version introduced
.NET 10
Previous behavior
Previously, dotnet watch emitted log messages to stdout.
New behavior
Starting in .NET 10, dotnet watch emits log messages to stderr.
Type of breaking change
This change is a behavioral change.
Reason for change
This change is part of a general trend towards dotnet CLI commands not obscuring the stdout channel, which is often reserved or assumed to have special semantics when running certain kinds of applications, like LSP or MCP servers. In general, the .NET CLI should get out of the way of your applications.
Recommended action
Most users shouldn't need to take any action. If you need the dotnet watch messages on stdout, you can redirect the stderr stream to stdout. For example, use 2>&1 to redirect the 2 file descriptor for stderr to the 1 file descriptor for stdout.
Affected APIs
None.
Schafft mat eis op GitHub zesummen
D'Quell fir dësen Inhalt kann op GitHub fonnt ginn, wou Dir och Theeme schafen an iwwerpréiwen kënnt an Ufroen unhuele kënnt. Fir méi Informatiounen, gitt op eisen Auteur-Guide.
