An option to enable/disable it within XbyK

[ChristopherBass]

Is your feature request related to a problem? Please describe.
A development team's shared development environment occasionally wants to have MiniProfiler available on a site for testing purposes, but wants to be able to turn it on conditionally with it defaulting to off (so it isn't running during every request).
Currently, because XbyK's MiniProfiler is turned on/off at app-start (in Program.cs), it is only activateable/deactivatable via an app restart.

Describe the solution you'd like
Potential solutions:

• An in-CMS setting of some sort (This would be the ideal, if a setting like that can be exposed somehow)
• A server cookie that, when active, enables MiniProfiler for that request. When missing, MiniProfiler does not run during that request
• A querystring that enables MiniProfiler for the duration of that request
• Some API endpoint in the MiniProfiler that would say 'activate/deactivate miniprofiler', to which we could attach our own logic

Describe alternatives you've considered
Editing the configuration files to add a setting that turns it on/off (and restarting the site if necessary) is cumbersome on sites where the environments are in a remote location (like Azure) with locked-down file access.

[seangwright]

We expose the options and follow up any customizations by forcing options.TrackConnectionOpenClose to be true in our extension call.

You can use this overload of the DI registration and then set options.ShouldProfile to be request based with a query param or something like that.

It would be up to you to conditionally enable the middleware per-environment.

[Sapphirress]

Hello @ChristopherBass, thank you for your feature suggestion. Does @seangwright's explanation help you solve this issue by yourself?
We are currently not inclined in delivering your proposed solution, unless we see more customers having the same need. Thanks for understanding.

[ChristopherBass]

I haven't had an opportunity to try it myself but I trust Sean's explanation, I'm sure I'll be able to use it when I'm back on that project.
Is this a common enough need to be worth adding his explanation to documentation?