Allow the Razor extension to report telemetry (and initialize) #79254
Conversation
) Fixes #12009 Needs a Roslyn bump before this will compile. Roslyn PR: dotnet/roslyn#79254
|
Was just offered the 2.87.31 update, read the changelog, and found these PRs related to telemetry: #79254, dotnet/razor#12015, dotnet/razor#12001. How can we disable such telemetry? |
|
I've no idea, but hopefully @dibarbet or maybe @timheuer knows? I should note, the changes in Razor are not introducing telemetry to the system, just reporting the existing telemetry through the Roslyn reporter instead of the Razor reporter for architectural reasons. If you've previously disabled telemetry reporting then that would still be in effect. Also, telemetry is only reported if you have the Dev Kit extension, with just the basic C# extension there is no telemetry. |
|
VSCode telemetry can be controlled by configuring |
Part of dotnet/razor#12009
Razor side: dotnet/razor#12015
Razor currently has a DevKit DLL to support telemetry in
rzls.exe, but for the assembly that runs in the language server as an extension, we had nothing. This allows us to report through the Roslyn reporter, which does the same DevKit stuff.Also creates a new initializer service we can provide, because previously we were abusing the dynamic file info system to get the workspace, and one day (with a bit of luck) that whole system will go away, so it's nice to remove a lynchpin.