Create a diagnostic notebook for user bug investigations

[jonsequitur]

We need to talk about what this does but I am currently thinking that we need a magic command that turns on / off the logging for components and perhaps the display of additional information.

For example - #r "nuget: ... blah " can produce an msbuild binary log file which significantly improves our ability to figure out why #r "nuget: " commands fail.

• [ ] Implement diagnostic

  !diag command args

  Details: Wire up basic diag command

• [ ] Implement: Command: #!diag location Details: Display the diagnostics location
• [ ] Implement: Command: #!diag logs path Details: Specify a target location for the diagnostic session artifacts
• [ ] Implement: Command: #!diag nuget full Details: Produces binlog and copies all #r nuget artifacts to the location specified in log_path
• [ ] Implement:
  Command: #!diag nuget display resolutions Details: Displays all resolved assemblies on screen
• [ ] Implement: Command: #!diag nuget display sources Details: Displays all specified nuget sources

Obviously I have spent more time diagnosing nuget issues, so I know what I want to see there, please add suggestions for other items that need diagnostics added and the type of information that would be usefull.

Another consideration, I have no opinion of ... 'well I do actually but I don't want to pollute the well' ... should the log information, such as log files location, nuget binlog file name, project file name be programmatically accessible as a value.

[RandomFractals]

this is good info: https://github.com/dotnet/interactive/blob/main/DEVELOPER-GUIDE.md#use-a-local-build-of-the-dotnet-interactive-tool

[jonsequitur]

We need to talk about what this does but I am currently thinking that we need a magic command that turns on / off the logging for components and perhaps the display of additional information.

We have this: #!log. I think the behavior is worth reviewing, though.