Please ship PerfViewCollect

TL;DR I think it would be convenient if I could download a PerfViewCollect.exe, rather than needing to build my own.

Today I wanted to compare a small possible memory allocation improvement, and in order to work around run to run variance, I want to run 10 times with my change and 10 times without. I didn't want to manually capture 20 runs, so I asked copilot cli to do it for me. One time I ran perfview.exe collect -?, which popped up a GUI with the help text that I had to copy and paste for copilot cli. The first time it tried to automatically capture traces it popped up 20 perfview windows, at least one of which had an error message and finished with "press enter to close". I don't know if it's because copilot's script tried to run 20 at the same time, or if the script expected perfview to act like a console app and not return control to the next statement until the process exited.

After finishing my experiment, I found this issue:

• https://github.com/microsoft/perfview/issues/1736

In that issue there's a comment that it's possible to build a CLI capture tool, which would have been ideal to use with copilot. But since it's not on the release page, I didn't know about it until I was prepared to file this new issue.

I would have benefit from the CLI capture tool a few times in the past, but now with AI tools like copilot CLI I think it's usefulness has increased. Please consider building and publishing it in addition to the GUI enabled perfview.exe.

Start by reading the related issue 1736 and inspecting how the current PerfView CLI capture tool is built and how releases are published. Determine what is needed to produce PerfViewCollect.exe alongside the GUI-enabled executable. Done means the CLI executable is built, published on the release page, and usable for non-interactive capture.