Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fields of specific type break the extension. #154

Open
algirdasN opened this issue Jan 30, 2024 · 0 comments
Open

Fields of specific type break the extension. #154

algirdasN opened this issue Jan 30, 2024 · 0 comments

Comments

@algirdasN
Copy link

Used Visual Studio

Visual Studio 2022

Are the latest Visual Studio updates installed?

No

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

N/A

Issue Description

Just by having a field of type System.Windows.Forms.ScreenOrientation anywhere in the project, it will break the SpecFlow extension with error:

The project bindings (e.g. step definitions) could not be discovered. Navigation, step completion and other features are disabled.

This might be related to other bugs here, however here I have a reliable way to trigger it. You may look at linked repository to see it in action.

Visual Studio - 17.7.7
SpecFlow Extension - 2022.1.91.26832

image

image

Steps to Reproduce

  1. Enable Windows forms in the project file (see repository for how-to).
  2. Create a field with type ScreenOrientation in you project.
  3. Rebuild the project (Ctrl+B).

Link to Repository Project

https://github.com/algirdasN/SpecFlowExtensionBug

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant