"Go to definition" from a .xaml.cs file leads me to .gics files instead of a .xaml file in Visual Studio 2015

Question

I am using Visual Studio Go to the definition (or ReSharper Ctrl+ left click) in the code behind the name of the element defined in XAML to pass me directly to the XAML of this element. For some reason this will lead me to a .g.i.csfile. Where this is not a huge problem, it is annoying like hell. This also does not apply to my project - I can create a new WPF project, add one button in XAML and get the same result to go to the button declaration in XAML from the code behind the file.

I tried to do the same in VS 2015 Professional on another computer and get the same problem.

But when I do this in Visual Studio Enterprise 2015 on my surface, it works correctly and switches to XAML (all tests performed using the new WPF project). I cannot find anywhere, wherever it is.

Any ideas for this would be greatly appreciated.

Answer 1

Well, it looks like ReSharper has actually changed the behavior - very naughty. I am pleased to say that ReSharper 9.2 fixed this problem (I used 9.1.3 first).