dotnet-watch redirects standard out to detect when the app is launched and prints these redirected messages to the console. Unfortunately once the app is launched, redirected messages are no longer printed. This wasn't caught earlier since ASP.NET Core is very quiet by default. ASP.NET Core apps launched via dotnet watch do not print output to the console. Yes. This was introduced as part of changes to dotnet-watch to launch a browser in 5.0-preview8. Low. |
||
|---|---|---|
| .. | ||
| Analyzers | ||
| Antiforgery | ||
| Azure | ||
| Components | ||
| Configuration.KeyPerFile | ||
| DataProtection | ||
| DefaultBuilder | ||
| Features/JsonPatch | ||
| FileProviders | ||
| Framework | ||
| Grpc | ||
| HealthChecks | ||
| Hosting | ||
| Html/Abstractions | ||
| Http | ||
| Identity | ||
| Installers | ||
| JSInterop | ||
| Localization | ||
| Logging.AzureAppServices | ||
| Middleware | ||
| MusicStore | ||
| Mvc | ||
| ObjectPool | ||
| ProjectTemplates | ||
| Razor | ||
| Security | ||
| Servers | ||
| Shared | ||
| SignalR | ||
| SiteExtensions | ||
| Testing | ||
| Tools | ||
| WebEncoders | ||
| submodules | ||