Include TFM in the pre-built report

[ViktorHofer]

The pre-built report that gets generated as part of the repo source-build would benefit from mentioning the TFM that brings the pre-built in. AFAIK there's a file that mentions the projects that bring the packages in and exactly in there the TFM would be extremely useful to mention.

The scenario here are repos that build both the previous and the current TFM in the repo source-build leg. Those need to understand whether pre-builts only affect the repo-source build or the product build. By mentioning the TFM in the report, that validation would become way easier.

The information is already available in the input source for generating the prebuilt reports, the project.assets.json files.

[MichaelSimons]

[Triage] @ViktorHofer - Do you have a sample use case where this would add value. So often the prebuilt report is just the starting point and you need to open the project.assets.json and/or binlog to gain a true understanding of the prebuilt.

[ViktorHofer]

@nohwnd reached out to me about this as he wasn't sure which pre-builts could be baselined and which ones truly affect the product build.

is just the starting point and you need to open the project.assets.json and/or binlog to gain a true understanding of the prebuilt.

Yes I agree that for more complex scenario you still want / need to look at the project.assets.json files or the actual source. Here I was thinking about the simple cases when $(NetPrevious) introduces a new prebuilt (for whatever reason) which should be baselined.

Note that mentioning the TFM in the error message is general goodness. MSBuild started doing sometime during the previous release and that helped me debug issues quicker.