Use the vscode extension "logPath" to dump the relevant information into a file, which we can directly ask the users for while dealing with issues on github

[akshita31]

vscode recently added "logPath" to be used by the extensions for some logging.

We can use this file to detect possible causes of failures lusing:

1. Omnisharp log
2. C# log
3. Mono path used by the extension
4. MSBuild instances used
5. dotnet --info
6. extension version
7. vscode version

The contents of this file can then be directly posted to the github issue and we will have better context of the problems the users face.

Questions:

• Whenever the extension is activated we will discard the old one and create a new file right ?

• What is the path of the file extensionpath/logging.txt ?

[akshita31]

cc @TheRealPiotrP @rchande Any other thing you think we should add ?

[akshita31]

This feature sounds similar to this feature in the powershell extension : https://github.com/PowerShell/vscode-powershell#2-capture-verbose-logs-and-send-them-to-us

[JoeRobich]

Closing due to lack of activity.