I am using SpecFlow in Visual Studio 2022. I have installed SpecFlow for Visual Studio 2022 extension. But I cannot find all SpecFlow templates when I want to Add New Item. I can find only three of them.
Can anyone help?
They are not there, because we didn't implement them for Visual Studio 2022.
This issue is https://github.com/SpecFlowOSS/SpecFlow.VS/issues/73
We are happy to add additional ones, but nobody yet answered me which of the missing ones you need.
Related
Is there a way to remove the Visual Studio project templates from showing up in Visual Studio 2019? I'm never going to use them and I've had multiple occurences where I accidentially created a new Visual Basic project instead of a C# project.
I've tried removing the physical files from Common7\IDE\ProjectTemplates and clearing the cache but the project templates keep showing up in the dialog.
to remove a template from Visual Studio you may use:
dotnet new --uninstall NAMEOFTEMPLATE.Template
to uninstall some project types (Visual Basic maybe) try Change Visual Studio Tool from Setup...
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.
I know there are already many threads on stackoverflow about this problem but they are all old and all the solutions work only for Visual Studio 2012/13. I'm using Visual Studio 2015 and I have the same problem.
I'm learning ASP.NET from a book and I've installed everything they have, and created the project exactly as they have but still can't see the 'Add Controller/Add View' options.
I've tried altering my ProjectGuids and that stuff but it is all incompatible since every solution I've found online is regarding older versions of Visual Studio.
Any ideas?
I downloaded visual studio 2015 and created asp.net vnext empty project.I added bower.json and grunt.js
When I define dependency, intellisense works fine for items but when I define item version intellisene not works and always says not available.
Only available since July 20th, 2015 on a Visual Studio update
more on it in Scott Guthrie blog post
I will suggest simply don't use VS 2015 just yet. It is good for some random checking and Hello World apps but i tried to convert my N-tier Enterprise application into V-Next MVC 6 using VS2015. It simple is not working for me.
VS keeps on restarting and it hangs when it goes to resolve dependencies automatically.
i did an upgrade and it caused lots of problems. unfortunately i didn't back it up. Is there anyway i can convert a 2010 solution file back into asp.net mvc 2008?
Make a backup of what's left of what you currently have before doing this ...
Create a new solution in Visual Studio 2008. Create new projects for the 2008 solution. Use the project menu or right-click the project and choose "Add Existing Items..." Choose all the code files .cs .vb, etc from your 2010 structure and include them in the 2008 structure.
Basically you're copying all the code back into a 2008 structure with the 2008 formatted project and solution files. The code shouldn't be substantially changed beyond repair. You might have to manually address some issues in the converted code but once you know what they are it will be a repetitive process more than anything.
If you are writing code of any importance you should be using a version control system like as SVN. I haven't tried Visual Studio 2010 yet, but can tell you from experience that the differences between 2005 and 2008 are laughably small. You can down convert a 2008 solution file by manually changing the first two lines from:
Microsoft Visual Studio Solution File, Format Version 10.00
Visual Studio 2008
to
Microsoft Visual Studio Solution File, Format Version 9.00
Visual Studio 2005
the project files are fairly trivial as well with the product tag changing from:
9.0.21022
to
8.0.50727
Please note the changes I have listed for project files may not be 100% accurate and I have not tested for differences between service pack releases. However, creating a new project in an earlier version of Visual studio, making a copy and then doing an upgrade should allow you to run a diff and provide a better answer than what is currently accepted.