Debug EBPF MSI - Doc update

[vpidatala94]

This is documentation update regarding runtime debug DLL of EBPF install instructions using Debug EBPF MSI.

Fixes #3872

[vpidatala94]

[lmb]

This means that having visual studio installed is enough for this to work? Is it possible to add a check to the installer to this effect?

[dthaler]

I this this is going in the wrong direction of requiring more action from users rather than less, and hence makes the developer story worse in my opinion.

[vpidatala94]

This means that having visual studio installed is enough for this to work? Is it possible to add a check to the installer to this effect?

the debug DLL should be in a location included %PATH% and readable by the EBPF services. The base requirement as I see are the debug DLL, coupling visual studio as a flag in the installer is unnecessary from my point of view. In a debug scenario the recommended way to install EBPF is using setup-ebpf.ps1 script, if the customer chooses to use the debug EBPF MSI, the above steps are recommended

[vpidatala94]

Hi Dave, wanted your thoughts on this issue again, the request was to investigate if the DEBUG MSI can run a script to copy the binaries to a select location (JIT subfolder) such that it can be picked up by the EBPF svc. Wanted to share my concern here Installers in general do not have external dependencies. This is an atypical scenario where we are not allowed to redistribute debug MSVCRT and static linking is not possible as well. My proposition is take the route of educating the customers using documentation to use setup-ebpf.ps1 script as the preferred way to install ebpf in debug mode or perform the manual steps of copying debug MSVCRT to the JIT subfolder.

[dthaler]

Hi Dave, wanted your thoughts on this issue again, the request was to investigate if the DEBUG MSI can run a script to copy the binaries to a select location (JIT subfolder) such that it can be picked up by the EBPF svc. Wanted to share my concern here Installers in general do not have external dependencies. This is an atypical scenario where we are not allowed to redistribute debug MSVCRT and static linking is not possible as well. My proposition is take the route of educating the customers using documentation to use setup-ebpf.ps1 script as the preferred way to install ebpf in debug mode or perform the manual steps of copying debug MSVCRT to the JIT subfolder.

We should not make developers lives difficult simply due to what we are allowed to do, when there is a way to not make their lives difficult. Users don't need to know whether there are external dependencies or not.