Skip to content

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

Closed
@sebastienros

Description

@sebastienros

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

Metadata

Metadata

Assignees

Labels

breaking-changeIndicates a .NET Core breaking change

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions