Source: https://github.com/dotnet/cli/pull/2145<p>Major violations of privacy happening in the .NET Core RC2 release. If you have anything even vaguely sensitive in your build scripts you may be in violation of your company's privacy rules. I expect massive lashback when this gets into the public eye but in the mean time be very careful using .NET Core RC2 in any sensitive projects.<p>Quotes from the first link:<p>"We collect the following pieces of data:<p>* The command being used (e.g. "build", "restore")<p>* Arguments passed to the command<p>* ExitCode of the command<p>* For test projects, the test runner being used<p>* Timestamp of invocation<p>* Details about the project commands are invoked on<p>* Framework used<p>* If RIDs are present in the "runtimes" node<p>* The CLI version being used"
I don't find it surprising that release candidates for an operating system are heavily instrumented. The goal of a release candidate is to find problems that didn't surface in the alpha and beta testing stages. Those will tend to be subtle corner cases.<p>Going further, phoning home is industry standard these days. Not just for Google or Apple operating systems but even Linux distros: e.g. Ubuntu.<p>I'm not saying it's right, just that it is not unique to Microsoft.
Clickable link: <a href="https://github.com/dotnet/cli/pull/2145" rel="nofollow">https://github.com/dotnet/cli/pull/2145</a><p>Sorry, I should have made the thread link directly to that issue.