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.
[LiveLogger] Plug the logger into minimum message importance checks
See original GitHub issueAs a perf optimization MSBuild can filter out verbose log output very early to speed up the build if no logger interested in low importance messages is enabled. LiveLogger is currently not recognized by this system, making it slower than the default console logger as configured in dotnet build.
It should be as simple as adding a case here: https://github.com/dotnet/msbuild/blob/dfd8f413a80cd0865f968b2c0ad9b09c0df8c430/src/Build/BackEnd/Components/Logging/LoggingService.cs#L1630-L1644
Needless to say, LL must not actually consume any low importance messages for this to work.
Issue Analytics
- State:
- Created 7 months ago
- Comments:7 (7 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
I think I would be comfortable with a string match on a fully-qualified type name in the code block in the OP.
Not a big fan of it, but it is a good enough hack for me, i think. I still would like to put some thought into LiveLogger location.