Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

specflow disabled, SpecflowPackagePackage didnt load correctly

enter image description hereI am having an issue with Specflow remaining disabled in Visual Studio extensions.

When I start VS I get an error SpecflowPackagePackage didn't load correctly.

I tried to uninstall and reinstall specflow but it seems weird. When I uninstall it says uninstall successful and asks to restart VS. When I restart Specflow is still there but disabled.

Using Visual Studio 2015, Update 3, 64bit. Windows 10. Specflow Version 2017.1.6

like image 766
Mateen-Hussain Avatar asked Mar 06 '17 17:03

Mateen-Hussain


People also ask

How to fix cannot find 'specflowsinglefilegenerator' error in Visual Studio?

Try injecting the scenario context to the binding class” If Visual Studio displays the error message Cannot find custom tool 'SpecFlowSingleFileGenerator' on this system. when right-clicking on a feature file and selecting Run Custom Tool, make sure the SpecFlow extension is installed and enabled.

How do I regenerate a feature file in SpecFlow?

Open a feature file in your solution. If you see a popup informing you that the feature files were generated with an earlier version of SpecFlow, click on Yes to regenerate these files. Depending on the size of your project, this may take a while.

How do I enable SpecFlow in Visual Studio 2017?

To enable the extension in Visual Studio, select Tools | Extensions and Updates…, select the “SpecFlow for Visual Studio” extension, then select Enable. You can enable traces for SpecFlow. Once tracing is enabled, a new SpecFlow pane is added to the output window showing diagnostic messages.

How do I fix the “outofprocess” error in SpecFlow?

If you are receiving this error, try setting the Generation Mode in SpecFlow to “OutOfProcess”. To do so: Select Tools | Options from the menu in Visual Studio. Select SpecFlow from the list on the left. Locate the Generation Mode setting and set it to “OutOfProcess”.


2 Answers

I had a similar problem. However, it's happened for me on Visual Studio 2017, then I went to Control Panel/Programs and updated the Visual Studio 2017. It's worked for me.

like image 142
Sérgio Bueno Avatar answered Sep 18 '22 12:09

Sérgio Bueno


I don't know what caused the problem. But the way I fixed was:

NOTE This might delete all plugins.

delete everything in below folders (with VS closed)

C:\Users\<username>\AppData\Local\Microsoft\VisualStudio\14.0
C:\Users\<username>\AppData\Roaming\Microsoft\VisualStudio\14.0

And reinstall the plugins along with specflow.

If someone can post a better answer please feel free to.

like image 26
Mateen-Hussain Avatar answered Sep 20 '22 12:09

Mateen-Hussain