Specflow Editor not working in Feature file after the latest - specflow

We are using Visual Studio 2017 and using Specflow as unit testing tool.
We have added "Specflow for Visual Studio 2017" as extension so that we have the editor in feature file.
Everything was working fine as expected and we were able to edit feature file. However after there was some upgrade from Specflow side, the editor is now not working
Any inputs ?

Related

Error : SpecFlow designer codebehind generation is not compatible with MSBuild codebehind generation

I am using visual studio 2019 in mac to setup my test automation framework in c# & Specflow . When i build my test automation framework in VS i am getting below error :
SpecFlow designer codebehind generation is not compatible with MSBuild codebehind generation. The custom tool must be removed from the file
On searching through forums, people recommending to remove the custom tool selected as "SpecFlowSingleFileGenerator". But when i check the same in VS 2019 for Mac it is not enabled for me to remove.
attaching the screenshotn. Can anyone help me with this issue ?
I'm not familiar with Visual Studio for Mac, but presumably the settings are the same or similar to Windows.
Check the SpecFlow options in Visual Studio. Make sure Enable SpecFlowSingleFileGenerator CustomTool is set to False. If Visual Studio for Mac is anything like windows, go to Tools > Options > SpecFlow, then look under the Legacy section.
A screenshot from Windows is below, showing the setting in question:

Codesmith generator 8.0, VS 2019 right click context menu does not have manage output option for .csp files

We upgraded to CodeSmith 8.0 from 5.2. We are using Visual Studio 2019.
I was able to upgrade the codesmith .cst templates. The right click menu on Visual studio 2019 solution explorer doesn't show Manage outputs, generate output or any of codesmith right click options for .csp files
It shows the right click options in windows explorer for .csp files but not for VS 2019.
See the two screenshots. Do I need to do anything special for the options to show up on VS 2019?
Right click menu from Windows explorer. There are code smith options when I right click on the .csp file
Visual Studio 2019
I work at CodeSmith Tools.. Microsoft broke the world with VS2019 and we are currently blocked by VSIX changes in VS2019 where Roslyn bin folder dependencies are not being deployed within the VSIX. This makes testing / development even more difficult. Until a fix is out we can't resume development of VS2019 as we can't even debug it :.

How to add language, platform and project type data to custom template in Visual Studio 2019

I have a extension which adds custom project template which is displayed under Installed -> Visual C# -> < type> in visual studio 2017.
but when i am using same extension in Visual studio 2019, on searching i get the template but without any label (like language, platform and project type).
and even if i select language filter in the wizard, i don't see the template in C#.
if any one can help, how to add language, platform, project type tag to the template.
Thanks
This is a VS 2019 issue. It has now been solved in visual studio 2019 version 16.1 Preview 2. However it has no backwards compatibility with previous visual studio versions.
For more information about the bug see: https://developercommunity.visualstudio.com/idea/422666/allow-custom-project-templates-for-custom-language.html
See https://learn.microsoft.com/en-us/visualstudio/ide/template-tags?view=vs-2019 for adding tags in visual studio 2019 Version > version 16.1 preview 2.

How can i add Jenkinsfile support to visual studio 2017

I am using Visual Studio 2017 Pro, and i am being driven crazy by the lack of syntax highlighting for the Jenkinsfile in my project. I am using the Declarative Syntax, but i just cant seem to find anything on getting this to work. My research says that its based on groovy, but i dont see a way to map it to that language either. Any help is appreciated.
This might not be a solution for everyone, but for me, it worked:
Jenkinsfiles are the only files without extension I am working with, therefore I opened
Tools -> Options -> Text Editor -> File Extensions
and then, I checked "Map extensionless files to:" and selected "Javascript Editor"
This does not require to install any extension and the display is great
I am in the same boat. Using Visual Studio 2017 Enterprise.
I found this extension recently for Visual Studio Code and this extension for Visual Studio.

cannot be opened. The project type is not supported by this installation

.cs project file
The project was created using Visual Studio 2010 and I am trying to open it in Visual Studio 2010 itself but still I am facing this problem.
I have opened this project in VS 2012 and worked for few days but it has created in Visual studio 2010. Is there anything which preserve the project details on local machine?
This is the specific project section in my solution file:
Microsoft Visual Studio Solution File, Format Version 12.00
# Visual Studio 2010
Project("{FAE04EC0-301F-11D3-BF4B-00C04F79EFBC}") = "Project Name", "Project Name\project name.csproj", "{48C1190E-7700-461B-ADCD-B5E0F1ECAD21}"
ProjectSection(ProjectDependencies) = postProject
{1F5440B3-9FD8-4FE2-B621-8697489ABDC4} = {1F5440B3-9FD8-4FE2-B621-8697489ABDC4}
EndProjectSection
EndProject
In Visual Studio it is possible to add Project Types, e.g. for creating an MSI, by installing an Add-On to the development machine. It appears that in the past this was done, and then that new Project Type was used to add a Project to the Solution. But now you are opening the Solution on a machine that does not have that new Project Type.
Look for the GUID of the missing Project Type, it should be part of the error you are getting. Then google "project type {the-guid}" to see which Add-On you need to install on your development machine.
It is also possible that a new Project Type was used in the Solution that simply can not work with VS 2010. In that case your options are either to keep using VS2012, or to start over with a new Solution in VS2010 and migrate the projects into it that are compatible (which may be a bit tricky or hard to do if VS2012 saved them).
Would it be too difficult to just recreate the project and include all the necessary files and references? Once the project was saved from VS 2012, the format may have broken compatibility with 2010. Sometimes this is fixable just by updating the version number in the project file, but I don't see it in your image.

Resources