We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
After opening the folder in this step (https://docs.microsoft.com/en-us/aspnet/core/tutorials/publish-to-azure-webapp-using-vscode?view=aspnetcore-3.1#through-visual-studio-code-interface), the OmniSharp log showed failures. These steps don't work with ms-vscode.csharp 1.21.10 and VSCode 1.41.1 on Mac 10.15.2. See OmniSharp/omnisharp-roslyn#1693 Downgrading to 1.21.9 appears to be a workaround.
Please make sure the ms-vscode.csharp Quality Assurance team is aware of these issues. This is a very poor first interaction with VSCode and Azure.
Les Steward
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.
The text was updated successfully, but these errors were encountered:
We have no connection to the OmniSharp team. Can you open a bug with them?
Sorry, something went wrong.
we have already resolved the issue in the pre-release 1.21.11 https://github.com/OmniSharp/omnisharp-vscode/releases/tag/v1.21.11
No branches or pull requests
After opening the folder in this step (https://docs.microsoft.com/en-us/aspnet/core/tutorials/publish-to-azure-webapp-using-vscode?view=aspnetcore-3.1#through-visual-studio-code-interface), the OmniSharp log showed failures. These steps don't work with ms-vscode.csharp 1.21.10 and VSCode 1.41.1 on Mac 10.15.2. See OmniSharp/omnisharp-roslyn#1693
Downgrading to 1.21.9 appears to be a workaround.
Please make sure the ms-vscode.csharp Quality Assurance team is aware of these issues. This is a very poor first interaction with VSCode and Azure.
Les Steward
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.
The text was updated successfully, but these errors were encountered: