Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

Specflow feature code behind file is not generated properly

Tags:

specflow

When I create a new feature file, then I am getting the below error in the code behind file

Could not find CodeBehindGenerator binary at location 
C:\USERS\XXXX\APPDATA\LOCAL\MICROSOFT\VISUALSTUDIO\15.0_A8FC0FAD\EXTENSIONS\0XCK4AN4.WWW\TechTalk.SpecFlow.VisualStudio.CodeBehindGenerator.exe.

Please open an issue at https://github.com/techtalk/SpecFlow/issues/

I have used the below packages

<package id="SpecFlow" version="2.4.0" targetFramework="net461" />
<package id="SpecFlow.CustomPlugin" version="2.4.0" targetFramework="net461" />
<package id="SpecFlow.MsTest" version="2.4.0" targetFramework="net461" />

Note: It was working til yesterday and suddenly the above mentioned error is throwing in the code behind file.

I have tried by upgrading the latest specflow version (3.0.188). But, still the above issue exist.

like image 531
Subburaj Avatar asked Mar 29 '19 06:03

Subburaj


People also ask

How do you regenerate SpecFlow feature files?

You can right click on the project and choose 'regenerate feature files' to do them all at once.

What is contained in the auto generated file for the SpecFlow feature?

Q #3) What is contained in the auto-generated file for the Specflow feature? Answer: Specflow code-behind files are auto-generated files with a “. cs” extension. These files have the binding logic from Steps to the actual Step definition.

How do I write a SpecFlow feature file?

Feature File CreationClick on Add, then select the option New Item. Add New Item pop-up comes up. Type SpecFlow Feature in the search box. Select the option SpecFlow Feature File from the search results.

How do I generate a CS feature in Visual Studio?

set Tools->Options->SpecFlow->Legacy->Enable SpecFlowSingleFileGenerator CustomTool = TRUE. Uninstall Tools->Extensions and updates -> SpecFlow for Visual Studio 2015. Restart Visual Studio. Install Tools->Extensions and updates -> SpecFlow for Visual Studio 2015.


1 Answers

This was an error in the VS Extension we updated yesterday.

See: https://github.com/techtalk/SpecFlow/issues/1456

New version will be published in the next hours.


The next time, please open an issue on GitHub and no Stack Overflow question. Thanks!

like image 195
Andreas Willich Avatar answered Jan 01 '23 08:01

Andreas Willich