Go To Definition (F12) not working

[Mat Walker]

Visual Studio 2013

'SpecFlow for Visual Studio 2013' - V1.9.3 - 2013/09/26 (Visual Studio 2013 Integration)

I'm kinda a noob to Specflow and thrashing my way around coming up to speed.  I'm working in an organisation that has a load of Solutions/Projects that use Specflow.  The person who did the Specflow stuff (I think) has left and some I am picking stuff up.  The guy obviously has/had a lot of Specflow knowledge as the projects and Specflow stuff are very well laid out with some great coding with the step definitions - as well as using common step classes etc...

The main issue I have (apart from my lack of full understanding yet :-)) is that right-clicking a a scenario step and selecting 'Go To Definition' is resulting in the 'No matching step binding found......' dialog.  The scenarios run ok, and if i debug, sticking a breakpoint in the set definition method, it shows the step defs being called ok.

I have done lots of searching for this issue and see it does go back to start of time; with most folk resolving it.  I have tried the 'fixes' given (IE. deleting temp cache files etc) but none have resolved it; hence this post.

If I create a new specflow project the  'Go To Definition' works great; it is just these projects that already exist.

I'm trying to understand how Specflow links to the method that is called when the step is executed; hoping that I will then be able to locate the issue and perhaps resolve it (increasing my understanding in the process....)

My current thought is 'I wonder it it is using an absolute path to the step defs file/s and my local copy - got from TFS - is in a different location.  But not got much further than that

So, when the  'Go To Definition' is selected in the IDE, what does SpecFlow do?  How does Specflow go about locating the method?  And, how does Specflow decide that one doesn't exist?

Any clues or suggestions of things I could look at would be gratefully received.  In the meantime I'll continue to dig.:-)

[Maria Nikolaeva]

Hi :)

I've just saw this issue.

Thanks for idea. It was problem in root name (git repository name). Original it was Automation. I've created local folder automation (lower case) and got this issue.

When I've renamed folder - f12 starts working.

[Gáspár Nagy]

Hi,

Could you please explain a bit more in detail, what the problem was and how you solved it? Maybe we can improve the handling in SpecFlow somehow.

Br,
Gaspar

[Bhupesh Dahal]

Has this been resolved ? 

F12 works for me when i have the step definition in the same project, but for step definitions that is pointing to external assembly I get "No matching step..", most of the times vsts freezes, but runs fine when i execute them. 

I am using specflow 2.0

Nunit -3.0

VSTS 2013