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.
Consider removing the `Microsoft.Build` package dependency, and the `TargetGraph` class.
See original GitHub issueThe StructuredLogger.MSBuild package depends on Microsoft.Build which is incompatible with .NET Standard 2.0 (“works” via the compatibility shim), weighs almost 4MB and brings quite many dependencies. It would be nice if we stopped depending on it.
Fortunately the only place where it is used is in TargetGraph, a class with relatively simple logic that is nowhere else used in this repro. Depending on your assessment of its importance and your appetite for breaking changes, we can:
- Just remove it.
- Obsolete it and remove it after a couple months/releases.
- Do nothing.
(and thank you very much for this project, it has allowed me to pierce inside dotnet build’s inner workings and helped me do lots of stuff with MSBuild!)
Issue Analytics
- State:
- Created 8 months ago
- Comments:5 (5 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
Cool, I have disabled TargetGraph.cs in this commit: https://github.com/KirillOsenkov/MSBuildStructuredLog/commit/f1a8e8b5fdaa8170a8818e47984ca01e2f06401a
Now you can remove Microsoft.Build too:
@teo-tsirpanis thanks!
Published https://www.nuget.org/packages/MSBuild.StructuredLogger/2.1.768