Skip to content

Microsoft.AspNetCore.SpaServices and NodeServices no longer fallback to console logger by default #14902

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
sebastienros opened this issue Oct 2, 2019 · 0 comments · Fixed by #15044
Assignees
Labels
breaking-change Indicates a .NET Core breaking change

Comments

@sebastienros
Copy link
Member

Microsoft.AspNetCore.SpaServices and NodeServices no longer fallback to console logger by default

From now on Microsoft.AspNetCore.SpaServices and Microsoft.AspNetCore.NodeServices would not display any console log when logging is not configured.

Version introduced

3.0

Old behavior

Microsoft.AspNetCore.SpaServices and Microsoft.AspNetCore.NodeServices used to automatically create a console logger when logging is not configured.

New behavior

Microsoft.AspNetCore.SpaServices and Microsoft.AspNetCore.NodeServices would not display any console log when logging is not configured.

Reason for change

To align them with how other AspNetCore packages implement logging we are removing this automatic fallback.

Recommended action

If the old behavior is required, to configure console logging please add services.AddLogging(builder => builder.AddConsole()) to your Setup.ConfigureServices method.

Category

ASP.NET Core

Affected APIs

Not detectable via API analysis


Issue metadata

  • Issue type: breaking-change
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
breaking-change Indicates a .NET Core breaking change
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants