This repository has been archived by the owner on Mar 29, 2021. It is now read-only.
Errors in the "Error List window" do not go to the correct line number #30
Labels
Comments
|
I'm not able to reproduce the behavior in a new solution. Would you be able to upload the smallest size solution that repros here? Also, what OS version and VS version are you using specifically? Update 1 / 2? |
esampsonite
added a commit
to esampsonite/TSLint.MSBuild
that referenced
this issue
Jun 3, 2016
…o to the correct line number
|
The PR #36 should fix this issue. I ran across this issue myself and dug into it a little deeper. The crux of the issue was only the first forward slash in the file path was being converted to a backslash. Once all of them were changed to backslashes, the problem was rectified. |
|
Great! |
JoshuaKGoldberg
pushed a commit
that referenced
this issue
Jun 6, 2016
* Issue #30 - Errors in the "Error List window" do not go to the correct line number * Target was executing when project was unloaded/loaded instead of just during build time
JoshuaKGoldberg
pushed a commit
that referenced
this issue
Jun 18, 2016
Includes fixes for #30 (incorrect slashes in output file paths), running when projects are loading, and a bug in the tslint version searcher.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
When double clicking an error in the "Error List window" in Visual Studio 2015, you are taken to the correct file, but not the correct line number and character.
The line number actually shows up correctly in the
Linecolumn in the "Error List window", but I'm not taken to the correct line number when clicking.Double clicking the line from the "Output window" takes me to the correct line and character.
Is anyone else seeing this behavior?
The text was updated successfully, but these errors were encountered: