Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
[Discussion] DebugLogger class made internal in ASP.NET Core 3.0
See original GitHub issueThe DebugLogger class was never intended to be constructed by user code. It is only constructed by the DebugLoggerProvider class. In 3.0 we are cleaning this up by making DebugLogger internal, to match with other logger implementations (such as ConsoleLogger, etc.).
This is the discussion issue for https://github.com/aspnet/Announcements/issues/367.
Issue Analytics
- State:
- Created 4 years ago
- Reactions:1
- Comments:5
Top Results From Across the Web
DebugLogger class made internal in ASP.NET Core 3.0
DebugLogger is now internal. Reason for change. Consistency and reduction of API surface. Recommended action. Use the the AddDebug ...
Read more >Breaking changes in .NET Core 3.0
For discussion on this issue, see dotnet/aspnetcore#19570. ... Logging: DebugLogger class made internal. Prior to ASP.NET Core 3.0 ...
Read more >ASP.NET Core breaking changes for versions 3.0 and 3.1
For discussion on this issue, see dotnet/aspnetcore#14996. ... Logging: DebugLogger class made internal. Prior to ASP.NET Core 3.0 ...
Read more >High-Performance Logging in .NET Core - Steve Gordon
In this post we explore high-performance logging for .NET Core applications using LoggerMessage.Define to reduce allocations and execution ...
Read more >c# - .Net core 3: The namespace internal does not exist in ...
I have a .Net core 2.1 project that was using the Microsoft.Extensions.Logging.Internal namespace, specifically FormattedLogValues class. I am ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Thanks for the response - this implementation has been around since ConsoleLogger was at 1.1.0, so I wouldn’t be surprised if it is past due for a rethink. I’ve got the same feeling about a more native solution than the current wrapper that I’m still working on and I’ll work with Glenn outside this thread as-needed.
Closing inactive discussion thread.
Note: Inactive closed issues are locked after 30 days since we don’t triage closed issues and new comments tend to be lost. Feel free to post a new issue if this issue is locked and you have further questions/discussions. See our issue management policies for more details.