Provide alternative for profiler loading settings

[iskiselev]

Currently, the only way to load a profiler is by enabling appropriate environment variables. I would be great to provide a way to load a profiler through some setting local to application - I've thought about Host Configuration Knobs. It will allow to install profiler though NuGet package, which may be convenient if profiler is used for dynamically updating IL or something similar task, when it is better to treat profiler as application component and application is not usable without profiler - or in APM scenarios with CI/CD, where APM agent will be convenient to treat as part of application.

Is there any design restrictions that will prevent it?

The main trouble will be found a way to resolve relative path to profiler library in case if application is not self-hosted.

cc: @noahfalk

[iskiselev]

It may also be tricky to find a solution that will work cross-platform, as different profiler library should be used.

[dotnet-policy-service]

Due to lack of recent activity, this issue has been marked as a candidate for backlog cleanup. It will be closed if no further activity occurs within 14 more days. Any new comment (by anyone, not necessarily the author) will undo this process.

This process is part of our issue cleanup automation.

[dotnet-policy-service]

This issue will now be closed since it had been marked no-recent-activity but received no further activity in the past 14 days. It is still possible to reopen or comment on the issue, but please note that the issue will be locked if it remains inactive for another 30 days.