Context menu options throw error in Project which has Step Bindings but no Feature Files

[jimcomiskey]

Used Visual Studio

Visual Studio 2022

Are the latest Visual Studio updates installed?

Yes

Content of reqnroll.json (if present)

{
"$schema": "https://schemas.reqnroll.net/reqnroll-config-latest.json",

"bindingAssemblies": [
{
"assembly": "Steps"
}
]
}

Issue Description

In Visual Studio, if I use a context menu to call "Find Step Definition Usages", I get the instances in feature files where that step is used. This works fine if the step definitions are located in the same project as the feature files. But if I move the steps to a separate project and reference them using bindingAssemblies, the context menu will throw an error stating "Unable to find step definition usages: the project is not detected to be a Reqnroll project or it is not initialized yet".

To work around this problem, if I add an empty feature file to the project holding the step assemblies, that passes the condition that checks if the project is a Reqnroll project, and it is able to detect the feature file from the other project that is referencing this step definition.

The problem will also occur if you use any other context menu option like "Rename step" or "Find unused step definitions"

Steps to Reproduce

I was able to reproduce this using the Reqnroll Project template. After creating this project, I add a new project to the solution and move the step definitions class to that project and reference the project using "bindingAssemblies" in reqnroll.json. The test executes fine, but if I try to call "Find step definition usages", it will throw an error.

Link to a project repository that reproduces the issue

No response

[gasparnagy]

See my comment here: #49 (comment)