Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Failures to obtain .NET runtime are not clearly surfaced in VSCode extension #2428

Closed
anthony-c-martin opened this issue Apr 26, 2021 · 3 comments · Fixed by #5871
Closed
Milestone

Comments

@anthony-c-martin
Copy link
Member

Created because of #2416.

We need a way of identifying the failure to obtain .NET and surfacing this error to users.

Under dotnet.showAcquisitionLog it looks like we have an option of opening a separate output channel, but it doesn't look like this would necessarily give our extension easy access to this information.

@StephenWeatherford may have some ideas on how to approach this.

@ghost ghost added the Needs: Triage 🔍 label Apr 26, 2021
@shenglol
Copy link
Contributor

When the Bicep extension is activated there will be a .NET Runtime output channel, which I believe is the one created by dotnet.showAcquisitionLog:

image

@alex-frankel
Copy link
Collaborator

Going to close since we know where this output stream lives now.

@anthony-c-martin
Copy link
Member Author

anthony-c-martin commented Aug 25, 2021

Reopening as discussed in today's triage. Capturing logs programatically is not possible through the VSCode APIs provided for the dotnet runtime extension. We however wanted to update the error message to give a pointer to the https://github.com/dotnet/vscode-dotnet-runtime repo or some instructions on error reporting, so that users know how to capture the right information.

@alex-frankel alex-frankel added this to the v1.0 milestone Sep 1, 2021
@ghost ghost locked as resolved and limited conversation to collaborators May 27, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants