SpecFlow extension for Visual Studio 2017 appears to install 1.9.0.77

[Richard Sinden]

Hi,

I've recently installed the SpecFlow extension for Visual studio 2017.
I have a project set up which references SpecFlow 2.1 and xUnit 2.1 (via Nuget).
Whenever I try and regenerate my SpecFlow features then I end up with a file generated by version 1.9.0.77 and that doesn't work with xUnit 2.1, because it uses the IUseFixture interface (from xUnit 1.X) rather than IClassInterface (from xUnit 2.X).
A dig around in the extension directory shows that the SpecFlow libraries installed are all version 1.9.0.77 and these are the ones it seems to be using to generate the files, even though the packages directory local to my project has the 2.1 libraries.

I feel like I must be doing something wrong, because according to the Visual Studio marketplace, the extension package hasn't been updated for 2 months, but I can't find anyone else complaining about it (unless I'm just not very good at looking).

If anyone could point me in the right direction, that would be very much appreciated.

Many thanks,

Richard

[Andreas Willich]

Hi

The Visual Studio Extension uses the SpecFlow version it finds in the package folder.

If it finds nothing, it falls back to the 1.9er version.

Try to turn on tracing and look if you find something in the output.

See "Enable Tracing" here: http://specflow.org/documentation/Troubleshooting-Visual-Studio-Integration/

BR

Andreas

--
You received this message because you are subscribed to the Google Groups "SpecFlow" group.
To unsubscribe from this group and stop receiving emails from it, send an email to specflow+u...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Richard Sinden]

Hi Andreas,

I reinstalled the various components, as I had already tried in various orders a few times, and this time it just worked. I'm not sure what I did differently to the previous times, and I didn't get the chance to run the trace on it.
For my own interest and possibly to help anyone else who hits the same problem, I thought I'd see if I could get it to break again and check the trace, but apparently not; It now works perfectly whatever I do.

Thanks very much for your swift reply and assistance.

Richard

[Nazareno Manco]

Hello, 

 I'm using VS2017 with SpecFlow and some collegues are using VS2015 with SpecFlow too.... 

My versions (2017) are: 

//      SpecFlow Version:1.9.0.77

//      SpecFlow Generator Version:1.9.0.0

//      Runtime Version:4.0.30319.42000

 

Their versions (2015) are: 

//      SpecFlow Version:2.1.0.0

//      SpecFlow Generator Version:2.0.0.0

Is it possible to align the versions or we get lots of warning 

Thank you

[Andreas Willich]

Hi 

Was the SpecFlow package restored to the packages- folder when you saved the feature file and the code behind file is generated?

Best regards

Andreas

--

[Nazareno Manco]

Hello... 

 sorry for the late reply. 

Yes, saved under "Packages\SpecFlow.2.1.0"

Best regards

Nazareno Manco

[jjvd...@yahoo.com]

Hi

Is there any way to influence this behaviour? We are using SpecFlow in a build system that does not work with NuGet, so we never have a SpecFlow dll in our packages folder. Therefore we will always get a 1.9.0.77 version of the file, which does not compile when using NUnit3... this means we cannot upgrade from NUnit2 to NUnit3...

I hope there is some way around this...

Cheers,

Jan-Jaap

[jason bouchard]

Same problem here.  Updated to the latest update for VS 2017.  I've now uninstalled and re-installed Specflow via 'extensions and updates'.  The version in VS 2017 is saying some GUID vs. an actual version of specflow like other extensions - maybe a clue.  Feature files are generating with 1.9.0.77.  See attached photos.

 

 

[jjvd...@yahoo.com]

We ended up generating the .cs files from msbuild, following these instructions:

http://specflow.org/documentation/Generate-Tests-from-MsBuild/

That solved our problem.

Cheers,

Jan-Jaap

[Yevgen Che]

Hi Andreas, 

could you please help me understand how can I get Specflow VS extension to use version 2.3.2.

I installed the latest version of Specflow from nuget to my project, yet I keep getting 1.9.* when installing VS extension. What am I doing wrong?

Thank you in advance

Br, 

Yevgen

On Thursday, May 11, 2017 at 8:06:30 PM UTC+2, Andreas Willich wrote: