Does anyone use Specflow 1.7.0 with Visual Studio Team System 2008? There are no Specflow templates available in “Add New Item” window after installation.
Installed previous version 1.6.1 and this time integration works fine. Any idea?
I have the same problem.
I was thinking it was because of a bad update of the msi version... but no.
Now : I need to create manually a .feature file
edit :
I have installed cuke4vs
https://github.com/henritersteeg/cuke4vs/downloads
now it's possible to to add features with "Add New Item"
(and in addition the feature file is colored :) )
Most probably found the bug.
Install the next nightly build from build.specflow.org, I hope it will work then.
Related
I am not able to determine, which version of the SpecFlow Visual Studio plugin I need to run the old version 2.2.0 of SpecFlow
Due to administrative constraints, we cannot use any other SpecFlow version than 2.2.0
I have tried several older versions of the VS plugin, but with my existing Code (based on SpecFlow 2.2.0), all these result in the error:
Error CS1029 #error: 'Version conflict - SpecFlow Visual Studio extension
attempted to use SpecFlow code-behind
generator 1.9, but project 'XXXXXXX' references SpecFlow 2.2.'
I suppose that I need some plugin Version, that works internally with 2.2
I cannot use the SpecFlow.Tools.MsBuild.Generation package, as this is not yet supported with 2.2.0.
Anyone can help me out? The release history of the SpecFlow Visual Studio Plugins can be found here:
https://github.com/techtalk/SpecFlow.VisualStudio/releases
EDIT
I use Visual Studio 2017 (15.9.6)
In the "packages" folder there are SpecFlow-2.2.0 and SpecFlow.MsTest-2.2.0. I deleted them, I deleted the nuget package Cache and rebuild the solution.
Problem still exists.
The error you are seeing has nothing to do with the suggestions in the comments. It is an additional check we added to the extension.
For SpecFlow 2.2 you have to use an older version of the extension. You can find them at https://github.com/techtalk/SpecFlow.VisualStudio/releases
When I am remembering correctly v2017.2.7 should work for it.
Don't forget to turn off automatic updates of the extension. If you do, you will get again the latest version.
Blog post about how to do it is here: https://specflow.org/2018/vs-integration-breaking-changes-affects-all-users/
Full disclosure: I am one of the SpecFlow and SpecFlow+ developers.
make sure you install the right Specflow extension for your VS(try uninstall and reinstall as well) also make sure you set "Enable SpecflowSingleFileGenerator to false" in VS>Tools>Options>Specflow. you only need this to be true for version 3 onward I suppose.
I had this issue, and while It worked to some extend however, I just install VS 2015 and use specflow 2.2 under that. you should be able to make it work for VS 17 I guess.
Here is my setup:
Specflow 3.0.191
Specflow.tools.MsBuild.Generation 3.0.191
Specflow.NUnit 3.0.191
Visual Studio 2019 Version 16
Deveroom Extension 1.1.1
When I am in a feature file in Visual Studio I am not able to go to the definition of any of my steps. I have tried F12 as well as right clicking on the step and choosing Go To Definition. Neither goes anywhere or pops any kind of error. There is a disconnect that doesn't prohibit the tests from running but does cause the Go To Definition not to work.
I have followed the configuration guide from the Specflow site (https://specflow.org/2019/updating-to-specflow-3/). My tests are running and working. I have deleted the specmap files from the %TEMP% directory and that didn't do anything. I uninstalled/reinstalled the deveroom Visual Studio plugin also which didn't work.
I welcome any insight.
Thanks,
J.R.
We are having the same issue with what I believe the root cause is the Visual Studio Extension version. According to the link you provided it should be supported by Specflow version 2.3.2 or higher, but we are still having issues with 2.4.1
A workaround for us was to uninstall the extension and then install the version appropriate .vsix file for the Visual Studio version below:
https://github.com/techtalk/SpecFlow.VisualStudio/releases/tag/v2017.2.7
And then remember to un-check automatic updates for this extension
I have been struggling with this for some time. I found that I had the following in my specflow.json config file:
{
"allowDebugGeneratedFiles": true
},
changing this to
{
"allowDebugGeneratedFiles": false
},
and rebuilding fixed the issue for me.
We are using the Google Test framework (version 1.7) for unit tests in C++ project (with Visual Studio 2012 and TFS 2012). By using GoogleTestRunner for VS2012 I am able to discover the tests written in Google Test within Visual Studio and run them. So far so good :)
Now I would like to run the tests with my CI build I have set up on our TFS. Therefore I have installed the GoogleTestRunner on my build server for the user that runs our build. If I run the build (and tests) on the build server directly in Visual Studio it works - but when the build is triggered by the TFS build definition I displays the following message in the log:
No test found. Make sure that installed test discoverers & executors,
platform & framework version settings are appropriate and try again.
Any suggestion what I am missing?
Is this working for anybody at all?
Your help is highly appreciated!
Christoph
I have been able to sort it out myself :)
There is a guide showing how to get it running for NUnit. Just follow that guide and adopt it to the GoogleTestRunner:
http://bartwullems.blogspot.de/2012/10/tfs-2012-build-configure-nunit-to-run.html
I extracted the DLLs from the GoogleTestRunner.vsix file with 7zip (I assume any other Zip program would work as well). I checked in all DLLs I found there (as described in the mentioned guide) - don't know if really all DLLs are needed.
Created a windows service in VS2012. Right clicked on the service and selected 'Add Installer' as done in VS2010
Got the message:
Unable to add installer. The designer could not add a Project Installer.
Anybody run into this ?
Check to see if the files already exist. In my case, a previous developer excluded the installer files from the project, so I did not see them until I opened a Windows Explorer on the source folder.
Do you have an Express version? I have not run into this problem with Visual Studio Professional 2012 on Windows 8 N Pro. I can right click on the designer surface and click on item "Add Installer" and a class is created called 'ProjectInstaller'.
You can create the project installer class manually. Designers are overrated anyway. I have written a blog article on how to do this.
Simple Installer for Windows Service Using Visual Studio 2012
Is there a reason you need a deployment wizard? Is there a configuration parameter you need to prompt the installing user with? I generally just use a configuration file and package up each environment's configuration with the deployable.
The Project Installer is not included in VS 2012. If you right click your solution and choose Add, New Project, then go to Other Project Types and choose Setup and Deployment, it should take you to the InstallShield page where you can download and install the Limited edition of InstallShield for free (you will have to register and get an activation code via email). Once installed, repeat the steps above and it should prompt you to either register the software or continue with a trial version.
We have a TFS build which outputs 2 exe's for 2 different solutions. How do I now integrate my build with InstallShield to use these exe's of both the solutions in my installer.
Any points to information would be greatly appreciated.
Thanks much in advance!!
There is no "as is" integration for this in TFS/MsBuild. You must open the msbuild script that TFS uses for each of your solutions and specify a target that will launch installshield.
If you use the integrated into VisualStudio version of InstallShield 2011, the setup can be part of the solution. But you have to install the stand alone version of InstallShield on TFS build machine. This done, InstallShield projects are built automatically by TFS, too.