Ambiguous step definition with new VS 2022 extension 2022.1.56.32801

[DomZZ]

Used Visual Studio

Visual Studio 2022

Are the latest Visual Studio updates installed?

Yes

SpecFlow Section in app.config or content of specflow.json

{ "$schema": "https://specflow.org/specflow-config.json", "generator": { "addNonParallelizableMarkerForTags": [ "nonparallelizable" ] }, "runtime": { "missingOrPendingStepsOutcome": "Error" }, "stepAssemblies": [ { "assembly": "ALOP" } ] }

Issue Description

Since visual studio extension upgraded itself to 2022.1.56.32801

All my step definition are ambiguous :

What I tried :

• Removed ".vs" folder
• Removed all existing .feature.cs files
• Uninstall extension and reinstall, it was the same

Runtime is OK, all tests are running like before.

Steps to Reproduce

I don't really know, it appears right after VS extension automatic upgrade ...

Link to Repository Project

I can provide my specflow project in private if needed

[DomZZ]

@SabotageAndi I've findout why I get the issue, this is due to the content of my specflow.json file : , "stepAssemblies": [ { "assembly": "ALOP" } ]

If I remove this, I don't get ambiguous steps errors !