.NET Alloc profiler activation on .NET (Core)

The .NET Alloc option requires the activation of a specific CLR profiler. The activation is implemented in PerfView by configuring HKLM\Software\Microsoft\.NETFramework\COR* registry keys. It does not seem to have any effect on my net7.0 application:

Is this behavior a configuration issue on my side?

I could not find any documented way to activate profilers from registry keys for the .NET (Core) runtime, so maybe it is a known and expected behavior.

However, if the profiler cannot be activated using registry keys, I suppose that PerfView should be improved:

• By explicitly documenting the behavior ("Collect" cannot enable the profiler and it must be manually enabled).
• By automatically configuring the expected environment variable when collecting with the "Run" action.

It can eventually create a PR for the last point.

Start by reproducing the reported Run/Collection matrix for net461 and net7.0, comparing registry-key activation with manual environment-variable activation. Inspect the profiler activation path used by PerfView; done means the .NET (Core) behavior is documented or the Run action configures the expected activation when collecting.