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
dotnet --info output: .NET Command Line Tools (1.0.4)
dotnet --info
Product Information: Version: 1.0.4 Commit SHA-1 hash: af1e6684fd
Runtime Environment: OS Name: ubuntu OS Version: 17.04 OS Platform: Linux RID: ubuntu.16.10-x64 Base Path: /usr/share/dotnet/sdk/1.0.4
VS Code version: 1.13.1
C# Extension version: 1.11.0
Build a project or test project which contains compilation errors e.g. missing semicolon
I expect that the build output error messages should be hyperlinked to the file line/character position they are associated with.
When building projects or if a test project fails to compile when running a test then the build output is not hyperlinked to the file/line number.
The only thing that is hyperlinked is the path of the .csproj file which isn't useful.
The text was updated successfully, but these errors were encountered:
This is a duplicate of #1197.
Sorry, something went wrong.
No branches or pull requests
Environment data
dotnet --info
output:.NET Command Line Tools (1.0.4)
Product Information:
Version: 1.0.4
Commit SHA-1 hash: af1e6684fd
Runtime Environment:
OS Name: ubuntu
OS Version: 17.04
OS Platform: Linux
RID: ubuntu.16.10-x64
Base Path: /usr/share/dotnet/sdk/1.0.4
VS Code version: 1.13.1
C# Extension version: 1.11.0
Steps to reproduce
Build a project or test project which contains compilation errors e.g. missing semicolon
Expected behavior
I expect that the build output error messages should be hyperlinked to the file line/character position they are associated with.
Actual behavior
When building projects or if a test project fails to compile when running a test then the build output is not hyperlinked to the file/line number.
The only thing that is hyperlinked is the path of the .csproj file which isn't useful.
The text was updated successfully, but these errors were encountered: