It's not a real problem, just a UI bug I think.
In toolbar, the profiling configuration
drop-down menu is also a button to run the current Run/Debug Configuration
. If you set the Run/Debug Configuration
to a normal .NET Static Method
(often Main
function), the profiling configuration button is enabled again. Click it will run the Main function and profiling it normally.
But you can't use this button to profile a unit test session.
Instead, this setting is automatically applied when you click Profile selected unit test
:
Just select the config you want, start the unit test, it will work.
This logic is more clear in menu. In the Run
menu, third item Profile XXX Using YYY
has a same icon with profiling configuration
. Hover the profiling configuration
button will show a tooltip contains a message equals the menu item.
And you can't run a unit test in Run
menu, there is a Tests
menu instead.
One more thing: Rider profiling support in Linux is incomplete, I recommend you do profiling things in Windows.