Move R2RDump over to the new System.CommandLine

[AndyAyersMS]

The System.CommandLine used by R2RDump is a defunct corefxlabs project. We should move it over to using the new System.CommandLine.

Among other things this will unblock porting some of the jitutils over to this new command line parser (since PMI needs to be able to run in Core_Root environment). See dotnet/jitutils#209.

[AndyAyersMS]

cc @trylek

I've been porting over jitutils so can do this too, if you like.

[AndyAyersMS]

Here's my first attempt: R2RDumpNewCommandLine

I ended up moving all the command line stuff over to DumpOption. Had to rename some things to get their binding model working.

Feel free to give it a try. You will likely run into dotnet/command-line-api#532 so that needs to be fixed before we can move forward.

In particular using the [parse] directive is kind of interesting:

dotnet exec D:\repos\coreclr\bin\Product\Windows_NT.x64.Debug\netcoreapp2.0\R2RDump.dll [parse] --in foo.dll -x -v -d -q bar -q baz --diff
[ R2RDump [ --in <foo.dll> ] [ -x <True> ] [ -v <True> ] [ -d <True> ] [ -q <bar> <baz> ] [ --diff <True> ] ]

[trylek]

Thanks so much @AndyAyersMS, it looks great to me, feel free to merge it in if it works for you; I doubt there are too many other users of the tool out there right now and we / they should get easily adjusted to the new syntax. After all I believe the pre-existing command-line syntax is super-overcomplicated and I'd love to clean that up somehow, I'm just somehow lacking the spare cycles to look into that :-(.

[ghost]

Due to lack of recent activity, this issue has been marked as a candidate for backlog cleanup. It will be closed if no further activity occurs within 14 more days. Any new comment (by anyone, not necessarily the author) will undo this process.

This process is part of our issue cleanup automation.

[ghost]

This issue will now be closed since it had been marked no-recent-activity but received no further activity in the past 14 days. It is still possible to reopen or comment on the issue, but please note that the issue will be locked if it remains inactive for another 30 days.