Carlos
Carlos
When the analysis fails (`BuildAnalyzer::Analyze`) we just return a `bool` to say whether it succeeded. The idea is to improve error messages because the analysis can fail before calling the...
If users want to perform the full analysis, they have to type `--analyze_all` (or add as many `--analyze_` options as desired). Can't we make this flag optional, and set by...
Example mangled name when analyzing a `CppBuildAnalyzer` `Debug|x64` trace: ??$_Seek_wrapped@V?$_Vector_iterator@V?$_Vector_val@U?$_Simple_types@PEAVTimelineEntry@@@std@@@std@@@std@@PEAPEAVTimelineEntry@@@std@@YAXAEAV?$_Vector_iterator@V?$_Vector_val@U?$_Simple_types@PEAVTimelineEntry@@@std@@@std@@@0@$$QEAPEAPEAVTimelineEntry@@@Z We're currently undecorating them in `src/AnalysisData/Utilities/CppBuildInsightsDataConversion.cpp`.
For now, exporters receive the `std::string` path to output their data. It would be useful to have them receive an `std::ostream` and let caller manage the creation of that stream.
Right now, every `.dll` in from project references ends up in the output folder. Is there a way to prevent most of them from being copied while still being able...
In order to support integration on build servers, it would be nice to have a new project that takes build configuration from command line and outputs the trace file. It...
We're using MSBuild 15 for now, targetting .NET Framework v4.6.2. It would be nice upgrading it to MSBuild 16, .NET Framework v4.7.2. When upgraded, it should be able to build...
Intermediate `Events.json` file contains messages with sensitive data. This includes: * System paths to compilers. * Solution, project and file paths. * Solution, project and file names. # Proposed solution...
To tell single-threaded compilations from multi-threaded compilations (those that have `/MP` enabled) we're parsing messages until we find these texts: * `Generating Code...` * `Compiling...` MSBuild seems to use the...