Ambiguous step definition with new VS 2022 extension 2022.1.56.32801

[DomZZ]

SpecFlow Version

3.9.74

Which test runner are you using?

NUnit

Test Runner Version Number

Nunit 3.13

.NET Implementation

.NET 5.0

Project Format of the SpecFlow project

Sdk-style project format

.feature.cs files are generated using

SpecFlow.Tools.MsBuild.Generation NuGet package

Test Execution Method

Visual Studio Test Explorer

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 :

I've removed ".vs" folder I've removed all existing .feature.cs files I also tried to uninstall extension and reinstall, it was the same

Steps to Reproduce

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

Link to Repro Project

No response

[DomZZ]

Runtime is OK, all tests are running like before. I can provide my specflow project in private if needed

[DomZZ]

I created a new issue in right repo : https://github.com/SpecFlowOSS/SpecFlow.VS/issues/78 I'm closing this one.

[github-actions[bot]]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.