Step 'Go To Definition' not working - shows 'Project Unavailable' message

[ejames]

Just started using SpecFlow and so far so good, except I am having
trouble navigating from feature files to coded step definitions.

- All feature files and step definitions are in the same project.

- When cursor is over a feature file step, pressing 'Go To Definition'
results in a message box reading "Project Unavailable". I expected to
be taken to the coded step definition or if none exists then a message
box with the stubbed out step definition.

How can I resolve this?

[ejames]

Fixed the issue with a VS restart. No issue to resolve.

[Alister Scott]

Issue happens continually for me (Latest Specflow with VS2010).
Any ideas besides VS2010 restart (which is annoying)?

[Pedro G. Dias]

+1 Not working here either. 

Environment: 

--> VS2012 RC, 

Package Config says: 

  <package id="SpecFlow" version="1.9.0" targetFramework="net40" />

  <package id="SpecRun.SpecFlow" version="1.0.0" />

Verified reference to SpecRun is 1.1.0

App.Config, relevant lines: 

 <ConfigSections>

         <section name="specFlow" type="TechTalk.SpecFlow.Configuration.ConfigurationSectionHandler, TechTalk.SpecFlow" />

  </ConfigSections>

...

  <specFlow>    

    <unitTestProvider name="SpecRun" />

    <plugins>

      <add name="SpecRun" />

    </plugins>

  </specFlow>

...etc...

[Gáspár Nagy]

Pedro,

Is this happening with the new (1.9) VS integration (from the VS
gallery?)?

Just to be sure: the correct package version for SpecRun.SpecFlow
should be 1.1.0.

Br,
Gaspar

On Aug 8, 9:14 am, "Pedro G. Dias" <pedro.digitald...@gmail.com>
wrote:

[Pedro G. Dias]

Gaspár, yes, this is happening with the 1.9 from the gallery. I tried it on a sample project that I have at home, and it's the same thing. 

The Specifications project is a unit test project, and the target framework is .Net 4.0 both for specifications and production code.

Screenshots of my configurations: 

Packages.config:

References in SpecFlow Specifications Project:

And finally, app.config: