When I press F12 (Go To Definition) in Visual Studio 2015 I get this error message:
One or more errors occured
I already tried:
Visual Studio 2015 Update 1 CTP fixes the issue.
This is an issue with C# and tabs instead of spaces when attempting to hit the metadata of an external assembly. It may be related the inferred position of the insertion point.
There are a couple of Connect tickets here and here and a Github issue on this. There is also a discussion here.
This issue is addressed in Update 1 so please install!
The options dialog remembers the last page and remains there on subsequent opens. I have a keyboard shortcut to open the options pane quickly (Alt + o). I am temporarily changing to spaces, going to definition and then reverting to tabs before making any code changes. This workflow isn't pretty but neither were the 3.0 Nuget issues in VS2015 either (Nuget 3 has improved to date).
This hack is no longer useful now that the Visual Studio bug is fixed. I'm leaving it here in case it's useful a sample for hacking around similar issues that come up.
AutoHotKey to the rescue! Fighting tirelessly against the evils of bad keyboard UX.
Here's how to set up a script that binds Ctrl+F12 to a key sequence that sets space indents, goes to the definition, and then restores tab indents. Use it instead of F12 to go to definitions outside your codebase:
FixF12.ahk
. Paste into it the script below.shell:startup
into the Windows Explorer location bar.FixF12.ahk
into Startup
and create a shortcut.Script for FixF12.ahk
:
#NoEnv
SendMode Input
^F12::
WinGetActiveTitle Title
IfInString Title, Microsoft Visual Studio
{
Send, ^QC{#} tabs{Enter}
Sleep, 300
Send, !p
Sleep, 300
Send, {Enter}
Send, {F12}
Send, !tO
Sleep, 300
Send, !k
Sleep, 300
Send, {Enter}
}
else
{
Send, {^F12}
}
The script is a hack, complete with flashing dialog boxes and a race condition, but it does the job. Don't forget to upvote the bug report in Connect. Hopefully Microsoft will release a fix before Update 1.
The Visual Studio 2015 Update 1 solved this problem!
VS 2015 Update 1 should fix this problem.
I have made an extension which simply enables/disables "Keep tabs" on each call of "GoToDefinition" command, and seems to work: GoToDefinition Fix
I found that; if you set Keep Tab under Option -> Text Editor -> All Languages -> Tabs, and it's the same under C#, the F12 and Alt + F12 Works just fine.