dotnet-dump analyze output to file

[crnegule]

Due to the way we interact with dotnet-dump analyze it would great to have a feature were we could output the results of a command to a file on the disk.
This feature would be similar to Out-File command from Microsoft.PowerShell.Core or similar to STDERR/STDOUT from C++ Redirecting from Command Prompt.
Would be willing to work on this if i get a recommendation where in the project this should be implemented.

[gfoidl]

You could redirect the output, e.g.

dotnet-dump analyze foo.dmp -c "eeheap -gc" > eeheap-gc.txt

Should work as #2169 is fixed.

[crnegule]

The feature i am referring to is inside the interactive dotnet-dump analyze instance. When we do the dump analysis to have the option to output the content without calling a new instance of dotnet-dump.

[michaelstum]

WinDBG had logopen/logappend which was VERY useful and pretty much a rule of thumb for me to always start every WinDBG session with a log open to capture everything. Running dotnet-dump -c works, but is a bit tedious if I still want an interactive shell to try out several things - I'd have to redirect to the output with the >> append redirect, open the logfile in some tail application to see the log output, then change the command line for every file. I guess I could build a frontend for that, but I'd really love to see dotnet-dump get native logopen/logappend/logclose functionality.

[mikem8361]

dup of #3095