|
|
|
|
|
by ptx
1521 days ago
|
|
Ah, yes, my mistake. Although PowerShell sends its own telemetry, the additional telemetry from the .NET platform is only sent when you use the dotnet command [1] and, as a special case, not when you very carefully invoke it only "in the following format: dotnet [path-to-app].dll" and never e.g. "dotnet help". However, presumably PowerShell requires at least the .NET Runtime if not the .NET SDK, doesn't it? The docs [2] suggest running "dotnet --list-runtimes" to "see which versions of the .NET runtime are currently installed", so it sounds like the Runtime also includes the dotnet command. Does running the recommended "dotnet --list-runtimes" command send telemetry, like most of the commands? Or are you saying that the Runtime, unlike the SDK, doesn't include telemetry at all? [1] https://docs.microsoft.com/en-us/dotnet/core/tools/telemetry [2] https://docs.microsoft.com/en-us/dotnet/core/install/how-to-... |
|
Nope, these days .NET programs (like PowerShell) bundle the runtime. But even if they did a lighter distribution that depended on the runtime already being installed, there would be no .NET telemetry sent.
> Does running the recommended "dotnet --list-runtimes" command send telemetry, like most of the commands?
This is still an SDK command. I don't personally know if this one sends any telemetry.
> Or are you saying that the Runtime, unlike the SDK, doesn't include telemetry at all?
The runtime does not send telemetry.