I am running VS 2015 and VS 2017 side-by-side. I have installed TechTalk's SpecFlow from Nuget plus Nunit, the same on both VS versions. When I try to Add New Item a new feature file I can do this on VS 2015 but on VS 2017 I can't see the SpecFlow feature template, or, indeed, any SpecFlow template. The reference to specflow is definitely in the references; there's a configsetting in the app.config for Specflow.
How do I start with SpecFlow in VS 2017 [v15.2 (26430.16) Release; .NET 4.6.01055; SpecFlow v2.2.0] ? Is SpecFlow even usable on VS 2017?
For item templates, intellisense and some other features you need to install the SpecFlow Visual Studio Extension in Visual Studio.
Extension for VS 2015: https://marketplace.visualstudio.com/items?itemName=TechTalkSpecFlowTeam.SpecFlowforVisualStudio2015
Extension for VS 2017: https://marketplace.visualstudio.com/items?itemName=TechTalkSpecFlowTeam.SpecFlowforVisualStudio2017
After installation you have the item templates available.
Andreas' answer is correct - the answer is to install the extension. However, the Download button on the URL above seems to do nothing, so it's best to install the extension from Visual Studio (select “Tools”, “Extensions and Updates…” from the menu. Click on "Online" on the left, and search for "SpecFlow") Make sure all your open instances of VS are closed down to complete the installation, then 'Modify'.
to use specflow in VS:
you need to install specflow extension (for your VS version)
then install specflow nuget package
it's better to restart VS in between.
for version < 3, then make sure you have "Enable SpecflowSingleFile Generator" set to false in (tools>options>specflow)
for version 3 onward, set to true
Related
Does anyone know if it is possible to update from Visual Studio 2017 to Preview version?
I don't want to install one more visual studio instance or reinstall existing one.
No, it's meant to be separate.
From https://www.visualstudio.com/vs/preview/
Side-by-Side
Preview installs next to your stable Visual Studio IDE, allowing you to use either independently
I am upgrading my project from visual studio 2010 to visual studio 2015
please tell me is there any need to upgraded the ms-build project.
Follow these steps to upgrade project created in earlier versions of VS this may help you:
In VS, on the File menu, click Open and then click Project/Solution,
Web Site, or File, depending on the kind of project you are
upgrading.
In the Open Project dialog box, select a project file, and then click
Open. If VS detects that the project or file was created in an earlier version of Visual Studio, the Visual Studio Conversion Wizard opens.
Complete the Visual Studio Conversion Wizard.
Refrence
is there any need to upgraded the ms-build project?
The answer is No. That because since start with Visual Studio 2013, Visual Studio team made a number of exciting changes to MSBuild for Visual Studio 2013. Now the 2013 version of MSBuild will ship as a part of Visual Studio instead of the .NET Framework. See this blog MSBuild is now part of Visual Studio! for more detail info.
You can find the MSBuild.exe from the directory: C:\Program Files (x86)\MSBuild\14.0\Bin
Since it ships as a part of Visual Studio 2013, just as Michael said, MSBuild upgrade should happen with the VS installation. So you do not need to upgrade the MSBuild separately.
Hope this helps.
I have StyleCop installed on my Visual Studio 2015. But, it does not give the option for running StyleCop on one particular file (on right click). StyleCop only runs on build. I am not getting the StyleCop setting option too. I have Visual Studio 2015 professional edition and I have install StyleCop from Codeplex. I have installed it using Nuget Package Manager.
You can try Visual StyleCop, which is an extension to Visual Studio. This preports to give the right click functionality into Visual Studio 2015
StyleCop.Analyzers gives you something close to the old right click functionality, but at a project level, not a file one. Let me know if you want more info on it.
Update 11 Feb 2016 There is an alpha release of StyleCop (4.
7.50) with Visual Studio 2015 support (but not C# 6).
Update 16 Oct 2018 StyleCop is mainstream available up to VS2017. Options in VS itself are provided by the extension, not the nuget package.
I can't find any Project Templates for Roslyn Extensions in the current released Visual Studio 2015 RC. Are they not available in the Release Candidate or just well hidden?
I am missing the whole Roslyn folder.
I have installed the Visual Studio 2015 SDK RC, do I still miss something?
They have moved to the Extensibility folder, and don't have Roslyn in the name. Instead they are named after what they actually do.
Additionally, they aren't part of the base Visual Studio install. You need to install the VS SDK, and the Roslyn templates VSIX at https://visualstudiogallery.msdn.microsoft.com/e2e07e91-9d0b-4944-ba40-e86bcbec1599.
I have a project in a solution I am working on in Visual Studio 2012, and I get this message for one of the projects: "This version of Visual Studio does not have the following project types installed, or does not support them." It is a vdproj. What does this mean and how do I resolve this problem
The correct procedure to resolve "Incompatible" issue with VDPROJ Projects coming from Visual Studio 2010 and 2015 in 2017 or 2019 is:
Enter Visual Studio .NET 2017 or 2019
2017: Click on "Tools" -> Extension and Updates -> Online
2019: Click on "Extensions" -> Manage Extensions -> Online
Type "Installer Project" on the search box
Click on "Install" in Microsoft Visual Studio Installer Project
Restart Visual Studio .NET and follow the instructions to install the extension
With this extension the old project (2010, 2015) is capable to work in (2017, 2019). VDPROJ are not deprecated, simply they are improved with a new extension, for more information about this please visit the oficial MarketPlace.
There is also the official:
Microsoft Visual Studio 2015 Installer Projects
Microsoft Visual Studio 2013 Installer Projects
Microsoft Visual Studio Installer Projects (2017 & 2019)
Microsoft Visual Studio 2022 Installer Projects
if you can jump to VS 2013, 2015, 2017+2019, or 2022
But BozoJoe is right, its time to drop vdproj and move on to WiX.
vdproj is a MSI creation project for Visual Studio. Its been deprecated and most people have moved on to either WIX or NSIS or a professional grade installer creation tools such as Install Shield.
If you do not require an installer for your product just exclude the vdproj project from the solution and continue with your life
for fun if you want to try to transition right away to wix, try this powershell script https://github.com/chrisoldwood/vdproj2wix
Visual Studio 2017 can use the Visual Studio Installer. It is NOT a default. You have to run InstallerProjects.vsix. You can get it at Microsoft Visual Studio 2017 Installer Projects. I have used it and worked great, at least for a windows GUI project. It's worth a shot before you get into the Install Shield intricacies.
if You use Microsoft Visual Studio Installer Project (Vs2017).
Microsoft Visual Studio Installer Project may be disabled after an update.
Tools -> Extensions and Updates..
Click Installed
Find and Select -> Microsoft Visual Studio Installer Project
do Enable
Restart Visual Studio