[dotnet-trace/dsrouter] simplify mobile tracing to a one-liner! #5542
  Add this suggestion to a batch that can be applied as a single commit.
  This suggestion is invalid because no changes were made to the code.
  Suggestions cannot be applied while the pull request is closed.
  Suggestions cannot be applied while viewing a subset of changes.
  Only one suggestion per line can be applied in a batch.
  Add this suggestion to a batch that can be applied as a single commit.
  Applying suggestions on deleted lines is not supported.
  You must change the existing code in this line in order to create a valid suggestion.
  Outdated suggestions cannot be applied.
  This suggestion has been applied or marked resolved.
  Suggestions cannot be applied from pending reviews.
  Suggestions cannot be applied on multi-line comments.
  Suggestions cannot be applied while the pull request is queued to merge.
  Suggestion cannot be applied right now. Please check back later.
  
    
  
    
This is WIP, I have a TODO list at the bottom.
This enables you to do:
Where
-p:DiagnosticSuspend=falseis optional.What this does:
dotnet-tracestartsdotnet-tracelaunchesdotnet-dsrouterpassing the--unmatchedargs along.
dotnet-dsrouterappends additional MSBuild properties if itdetects the unmatched args are a
dotnet buildordotnet runcommands
dotnet-dsrouterlaunches the command for the unmatched args.TODO
Merge this one first: [dsrouter] improved instructions/log messages #5535
Figure out how we show progress.
dotnet build -t:Runcan take30 seconds+, so it seems like we somehow need to let the terminal
logger show progress? Not sure how that can work.
Switches after the
--must be quoted in some cases:'-t:Run'for example. This is also a problem with plain
dotnet-trace. Thiscould maybe be addressed in a separate PR.
For iOS, we may want to pass
-p:_MlaunchWaitForExit=falsesothat it doesn't block on console output. That would mean we might
also want the MSBuild property to be public.