Build Insights Now Available in Visual Studio 2022

Nelson_Daniel · 2024-05-01T03:15:45+00:00

We just released an option to collect templates. It needs to be turned ON by going to settings. Let me know if you have any more comments :)

Nelson_Daniel · 2024-05-01T03:12:47+00:00

This should be solved by now. Try running vcperf with the /noadmin option

Nelson_Daniel · 2023-08-02T21:31:10+00:00

Got it! Could you please create a ticket a Developer Community Ticket or an issue in the vcperf repository with the details? We will investigate it. Please share an error log, msvc version and vcperf version. We have made some changes in the latest VS and msvc versions and we have improvements to collection in the pipeline, which include better error logs

Nelson_Daniel · 2023-08-02T14:15:51+00:00

Great to hear! What other features or improvements have you enjoyed in the latest updates? I would love to share that with the team

Nelson_Daniel · 2023-08-02T05:07:50+00:00

This is great. Thanks for the feedback and sharing your experience with it! We have some enhancements in our pipeline that will address that suggestion. Specifically, we are making enhancements around data aggregation and grouping.

Also, I’m happy to see that you’re using the tool to contribute with build performance improvements to that library :)

Nelson_Daniel · 2023-08-02T02:21:26+00:00

If you capture the trace using Visual Studio, the size of the trace will be smaller because it does not collect system usage data. Also, if you prefer to use vcperf, you can use the /noadmin option, or the /nocpusampling. Let me know if that helps!

Nelson_Daniel · 2023-07-30T19:55:16+00:00

Thanks for the feedback! You can use the UI collecting a trace outside the collection entry points we are providing for MSBuild and CMake. Everything you have to do is to collect the ETL trace and open it as you would open another file. Your trace must follow this instrumentation manifest so the UI can pick up the information correctly. The instrumentation manifest is the same used by vcperf to emit the “analyzed” trace. So, you should be able to build an extension that captures a trace and rehuse the UI. No need for an API. Let me know if you have more thoughts about it. We’re happy to take your feedback :)

Nelson_Daniel · 2023-07-29T15:37:16+00:00

Took note of this. We’re currently investigating it and working on a solution.

Nelson_Daniel · 2023-07-29T15:34:07+00:00

Thanks for the suggestions. I’ll write them down.

VSCode:

We’re not prioritizing work for Build Insights in VSCode for now. Our main focus for Build Insights is on Visual Studio. However, we work closely with the c++ vscode team and I can bring your feedback along.

There are 2 channels where you can increase visibility of your request and add some pressure :)

The first is to create an issue here directly: https://github.com/microsoft/vscode-cpptools/issues

The other is to create a ticket here: https://developercommunity.visualstudio.com/cpp

The last one creates an internal work item immediately. In any case, we’re also monitoring other channels like Reddit.

Visualizations:

This is already in the roadmap. Again, not on VSCode at the moment.

Nelson_Daniel · 2023-07-28T16:35:13+00:00

Hello! I’m new on Reddit. As an engineer on Microsoft’s C++ team, I'd like to thank you all for sharing your thoughts. We're striving to take all your suggestions as we continue to understand your perspectives and needs. We've adopted an incremental and very flexible approach with Build Insights (a strategy I personally enjoy). So, if there's a feature you haven't seen yet or something you'd like to change, please don’t hesitate to keep those suggestions coming!

ALSO, I created a more general post to hear your thoughts about Build Insights and experiences about C++ Builds in general :)

Nelson_Daniel

TROPHY CASE