SpecFlow creates a .cache file in your Temp folder that holds these bindings to speed things up. If that file gets out of whack, you can delete it:
- Exit Visual Studio.
- Open Windows Explorer.
- In the address bar, type %TEMP% and hit Enter to go to your temp folder.
- Find the files whose names start with “specflow-stepmap-YourProjectName” with a .cache extension.
- Delete those files.
- Start Visual Studio again.
If you do this, it’ll take a little time for SpecFlow to regenerate the bindings. Until this is done, if you right-click on a step and select “Go To Step Definition”, Visual Studio will reply “Step bindings are still being analyzed. Please wait.”
I most commonly use this for the opposite case, where SpecFlow shows that nothing is bound even though the steps exist. But I think it’s likely to work for your case as well.