Update for Microsoft Visual Studio 2015 Update 3

AndreTen · 12 Jun 2016

No words of dropping the telemetry in C++ compiler.

dmex · 12 Jun 2016

AndreTen said:

No words of dropping the telemetry in C++ compiler.

The so called "telemetry" was located in the CRT, not the C++ compiler and it's been removed in this update.

AndreTen · 12 Jun 2016

dmex said:

The so called "telemetry" was located in the CRT, not the C++ compiler and it's been removed in this update.

Of course, but new sources like Betanews, Softpedia, etc are referring to latter rather than CRT. This is why my question was like it was.

If I mentioned it, it would be appropriate to quote MS representative also (from Betanews, but they quoted also):

Our intent was benign -- our desire was to build a framework that will help investigate performance problems and improve the quality of our optimizer should we get any reports of slowdowns or endemic perf problems in the field.
We apologize for raising the suspicion levels even further by not including the CRT source, this was just an oversight on our part. Despite that, some of you already investigated how this mechanism works in nice detail. As you have already called out, what the code does is trigger an ETW event which, when it’s turned on, will emit timestamps and module loads events. The event data can only be interpreted if a customer gives us symbol information (i.e. PDBs) so this data is only applicable to customers that are actively seeking help from us and are willing to share these PDBs as part of their investigation. We haven’t actually gone through this full exercise with any customers to date though, and we are so far relying on our established approaches to investigate and address potential problems instead.