4 ms·
> I don't see how it's unexpected when you get a message telling you when you first run it - and the only thing to do with this tool is to run commands explicit
by flukus 9y ago
> I don't see how it's unexpected when you get a message telling you when you first run it - and the only thing to do with this tool is to run commands explicitly.
What about when it's run through VS or some other tool that hides much of the text? How does it know that I've read this information when it could be buried in several thousand lines of output from itself and other tools like make or msbuild?
Being explicit about opt-out is even less acceptable for command line tools than it is GUI based ones.
- cjsuk 9y agoExactly. It only takes one misconfiguration for your build server to call home. It should take one misconfiguration for your hold server to not call home. Slightly subtle inversion there.
- benaadams 9y ago> What about when it's run through VS or some other tool that hides much of the text? VS uses MSBuild rather than the dotnet cli (its also what the dotnet cli calls)