You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As part of updating the Microsoft.AspNetcore.Mvc.Core assembly to use LoggerMessageAttribute, we discovered logger event Ids being reused within a single log category. Log IDs and names should be unique so different message types can be identified. Consequently, these have been updated to ensure that the event Ids are unique for a logger category.
Version
.NET 7
Previous behavior
Some logger event IDs in Microsoft.AspNetCore.Mvc.Core were re-used within a single category.
New behavior
Duplicated event ids within a single category within the Microsoft.AspNetCore.Mvc.Core assembly were updated.
Type of breaking change
Binary incompatible: Existing binaries may encounter a breaking change in behavior, such as failure to load/execute or different run-time behavior.
Source incompatible: Source code may encounter a breaking change in behavior when targeting the new runtime/component/SDK, such as compile errors or different run-time behavior.
Reason for change
Log IDs and names should be unique so different message types can be identified.
Recommended action
If you have code or configuration that references the old IDs, update those references to use the new IDs.
Affected APIs
Not detectable via API analysis
The text was updated successfully, but these errors were encountered:
Description
As part of updating the Microsoft.AspNetcore.Mvc.Core assembly to use
LoggerMessageAttribute
, we discovered logger event Ids being reused within a single log category. Log IDs and names should be unique so different message types can be identified. Consequently, these have been updated to ensure that the event Ids are unique for a logger category.Version
.NET 7
Previous behavior
Some logger event IDs in Microsoft.AspNetCore.Mvc.Core were re-used within a single category.
New behavior
Duplicated event ids within a single category within the Microsoft.AspNetCore.Mvc.Core assembly were updated.
Type of breaking change
Reason for change
Log IDs and names should be unique so different message types can be identified.
Recommended action
If you have code or configuration that references the old IDs, update those references to use the new IDs.
Affected APIs
Not detectable via API analysis
The text was updated successfully, but these errors were encountered: