Closed MarkKharitonov closed 2 years ago
The VS extension is at fault. It records incomplete binlogs and their repo has a few bugs about it. That extension is not maintained at the moment.
I see. Too bad. Thank you.
Are there any plans to produce your own extension for Visual Studio? Would be a logical step...
I have no plans to do anything for Visual Studio unfortunately.
In the past, the
Weird enough, there is no information about the task parameters either.
CoreCompile
target node in the viewer provided a reason for it being called just because there are Inputs and Outputs on the target. I have noticed today that no such reason is provided anymore:This binary log is created using the Project System Tools extension for Visual Studio. The one created by msbuild seems fine:![image](https://user-images.githubusercontent.com/489792/154572669-bb214c8a-c4b8-49c0-ad2a-678d8a8d0b38.png)
Is this the log viewer's issue or Visual Studio's or the extension is at fault?
I am using VS 2022.