David Fowler

dotnet tools shouldn't error if no arguments are provided

2

Just print the help and drop the "Required command was not provided." .e.g ``` root@004561cfab39:/# dotnet counters Required command was not provided. Usage: dotnet-counters [options] [command] Options: --version Display version...

dotnet dump analyze should work with x86 and x64 dumps seamlessly

7

- [ ] - Support debugging 32 bit dumps without manually invoking the 32 bit dotnet host. - [ ] - Using 32 bit dump with 32 bit `dotnet dump...

Improve scenarios where dump analyze commands spew lots of output

1

With larger dumps, some of the `sos` commands are much harder to use as they spew lots of output and which can be hard to cancel. We could do a...

dotnet dump collect should generate dump with process name in the dump name

1

``` C:\Users\david\Desktop\dumps> dotnet dump collect -p 37444 Writing minidump with heap to C:\Users\david\Desktop\dumps\dump_20191005_154551.dmp Complete ``` In that random name should have the name of the main module (ConsoleApplication1 or WebApplication1...

I'd like to see a summary of the queues without dumping the work items themselves: ``` Statistics: MT Count TotalSize Class Name 00007ff831723fb0 2 272 System.Runtime.CompilerServices.AsyncTaskMethodBuilder`1+AsyncStateMachineBox`1[[Microsoft.AspNetCore.Connections.ConnectionContext, Microsoft.AspNetCore.Connections.Abstractions],[Microsoft.AspNetCore.Server.Kestrel.Transport.Sockets.SocketConnectionListener+d__13, Microsoft.AspNetCore.Server.Kestrel.Transport.Sockets]] 00007ff83187dc08 1...

It shows everything but the filter data: ``` Provider Name Keywords Level Enabled By Microsoft-Extensions-Logging 0x000000000000000C Error(2) --providers Process : /apps/AspNetCoreDiagnosticScenarios/Scenarios/bin/Debug/netcoreapp3.0/Scenarios Output File : /apps/AspNetCoreDiagnosticScenarios/Scenarios/trace.nettrace [00:00:00:00] Recording trace 102.00 (B)...

Extract EventPipeEventSource from TraceEvent and make it part of Microsoft.Diagnostics.NetCore.Client

1

There are a couple of reasons we should do this: - TraceEvent is large and has too many dependencies - It's unfortunate that the logic to read events isn't part...