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:
I have a web application developed in Visual Studio 2019 (free Community edition), running on .NET Core 2.2
Because it's a web app, unit tests don't really help. But I would like to see if I have tested all the code when doing manual testing. Is this possible?
If you care to suggest a way of automating the testing of a complex web app, that would be nice, provided it isn't too open ended a question.
Maybe it's very easy but I'm trying to add support for xUnit in Visual Web Developer 2010 Express. I followed this tutorial on how to install everything but the main problem is that this tutorial only show how to add a test project to a new project and not to an existing one. When I do "Add New Project", there is not "xunit" or "test project" anywhere...
Anybody know how or can point me to a good tutorial?
A standard Windows Library (.DLL) project will work fine and is the normal project type used for xUnit.net Tests - all the existing mechanism really added was the inclusion of some example tests to start you off.
This (not having templates) is the approach being taken with future xUnit versions. You'll find some discussion of the reasoning behind this on http://xunit.codeplex.com/discussions
When I create a New Project of type ASP.Net MVC Web Application, I expect the dialog for unit test applications to show up, but it does not. I cannot find the Unit Test App among the product types I can create either. How do I set up my VS so that the dialog shows up?
I have installed Visual Studio 2008, .Net Framework 3.5 SP1 and ASP.Net MVC Framework (Beta).
As #MrJavaGuy says, you need to install at least the Professional, not Express, version of VS2008. Alternatively, you can install nUnit and/or TestDriven.Net and get unit testing capabilities. Info on nUnit can be found at http://www.nunit.org/ and TestDriven.Net at http://www.testdriven.net/. I recommend TestDriven.Net even if you have the testing capabilities of Visual Studio baked in.
Turns out one of the problems were that I hadn't installed Testing Capabilities with my VS installation - running the installer and adding the feature made everything roll smoothly =)
Had the same problem with Visual Web Developer Express, I found this blog.
http://blogs.msdn.com/webdevtools/archive/2008/05/30/asp-net-mvc-preview-3-tooling-updates.aspx
I downloaded
http://www.box.net/shared/zmp0cdxsss
and that worked for me.. Not sure if this will sort your issue though. Best of luck with it.
What is "missing" in the Visual Studio 2008 Express Editions?
In particular,
what functionality is not available?
what restrictions are there on its use?
The major areas where Visual Studio Express lacks features compared to Visual Studio Professional:
No add-ins/macros
Some Win32 tools missing
No Team Explorer support
Limited refactoring support
Debugging is much more limited (particularly problematic for server development is no remote debugging)
Lack of support for setup projects
No report creation tools
No Office development support
No mobile platform support
Limited set of designers
Limited set of database tools
No code profiling or test framework support
No MFC/ATL support
No support for compiling C++ to 64-bit images (workaround is to install Windows SDK which is free)
NOTE: it is often said that the Express EULA does not permit commercial development - that is not true (Visual Studio Express FAQ Item 7)
There's a handy set of comparison charts on microsoft.com.
It depends on the particular express edition, of course (since there are several and they have different features). The limitations you're most likely to run into are source control integration (and TFS client license), debugging limitations, limited refactorings, no unit testing support, and limited designer support.
For completeness sake, here's a list of features that are in Visual Studio 2008 Standard Edition but are in none of the express editions:
Add-Ins
Macros and Macros IDE
Visual Studio Add-in project template
VSPackages
Wizards
ATL/MFC Trace Tool
Create GUID
Dotfuscator Community Edition
Error Lookup
Source Control Integration
Spy++
Team Explorer Integration
Team Foundation Server Client Access License
Visual Studio 2008 Image Library
Add-Ins/Macro Security options
Visual Studio Settings
Class Designer
Encapsulate Field Refactoring
Extract Interface Refactoring
Promote Local Variable to Parameter Refactoring
Remove Parameters Refactoring
Reorder Parameters Refactoring
Debugging Dumps
JIT Debugging
Mini-dumps
Multithreaded/Multiprocess Debugging
NTSD Command Support
Step-Into Web Services Debugging
CAB Project Project Template
Merge Module Project Template
Publish Web Site Utility
Setup Project Template
Setup Wizard Project Template
Smart Device CAB Project Template
Web Setup Project Template
Windows Installer Deployment
64-bit Visual C++ Tools
Create XSD Schema from an XML Document
Reports Application Project Template
Visual Studio Report Designer
Visual Studio Report Wizard
Shared Add-in Project Template
ASP.NET AJAX Server Control Extender Project Template
ASP.NET AJAX Server Control Project Template
ASP.NET Reports Web Site project template
ASP.NET Server Control Project Template
ASP.NET Web Application Project Template
Generate Local Resources
WCF Service Host
WCF Service Library Project Template
WF Activity Designer
Custom Wizard Project Template
WF Empty Workflow Project Template
MFC ActiveX Control Project Template
MFC Application Project Template
MFC DLL Project Template
WF Sequential Workflow Console Application Project Template
WF Sequential Workflow Library Project Template
WF Sequential Workflow Service Library Project Template
WF State Machine Workflow Library Project Template
WF State Machine Workflow Designer
WF State Machine Workflow Service Library Project Template
WCF Syndication Service Library Project Template
Visual Studio Extensions for Windows Workflow Foundation Designer
Windows Forms Control Library Project Template
Windows Service Project Template
WF Workflow Activity Library Project Template
WPF Custom Control Library Project Template
WPF User Control Library Project Template
ASP.NET Server Control Item Template
COM Class Item Template
Configuration File Item Template
Frameset Item Template
Interface Item Template
CLR Installer Class Item Template
Local Database Cache Item Template
Module-Definition File Item Template
Nested Master Page Item Template
ATL Registration Script Item Template
MS Report Item Template
Report Wizard Item Template
.NET Resources File Item Template
Win32 Resource File Item Template
Static Discovery File (Web Services) Item Template
Transactional Component Item Template
Web Content Form Item Template
Windows Script Host Item Template
Windows Services Item Template
XML Schema Item Template
Here's comparison chart of editions
Edit: didn't realize this was for 2005, not 2008
Visual Studio 2008 Product Comparison
As far as I know there are no restrictions on its use, but I'm not a lawyer.
AviewAnew pointed out you can use Express Editions for commercial use: there are no licensing restrictions for applications built using Visual Studio Express Editions. See FAQ #7.
These are the most significant for me:
You cannot set breakpoints with a condition
Add-in support
Refactoring is very limited (rename, extract method)
MFC is the most important missing thing in my opinion.
No add-ins allowed
Other people have posted huge lists, but as a practical matter, speaking as someone who does mostly systems programming, the features I miss most when using the express edition are
the thread-aware parts of the debugger,and
the ability to open files with the built-in binary viewer.
If I did MFC programming more often I would probably miss the dialog designer as well.
One that is missing (which is nice to have) is:
Source Control Integration
enables two
options: source control solution based
on the Source Control Plug-in API
(formerly known as the MSSCCI API), or
a source control VSPackage
This is particularly important especially if you're working with systems like Perforce where you must check out files before changing with them, particularly changing project settings for all team members.
This MSDN document should get you everything you need!
Note that currently, you can't get F# in an Express edition, though I imagine that this is likely to change at some point in time.
There is a workaround - you install the Visual Studio Shell and F# CTP separately and they work together.
I had trouble with Visual Studio Express (C++) 2008 (with service pack 1) on Windows Vista, with debugging. Any time I did anything such as (a) break the program, (b) set focus from the app back to the IDE, (c) resume execution, the program hung for about 30 seconds. Task Manager showed "VSExpress.exe" consuming an entire CPU for the duration. Vista showed "Not responding" in the IDE's title bar during this time.
This was driving me bonkers so I bought a commercial copy of Visual Studio Professional 2008 ($150 from SoftwareSurplus) and this solved the problem.
For Visual Studio 2008, the Express editions do not have the built-in testing features for one.
You can build MFC applications if you download the libraries in the Platform SDK. But there is no built in support for designing dialogs.
Add-ins are allowed in Visual Studio Express. The most notable one is straight from Microsoft: XNA Game Studio works as a Visual Studio Express add-in.
There's even a project type (maybe only available in the full Visual Studio) that lets you build your own Visual Studio Express add-ins!
You can't create Windows services for one.