I had Studio 2019 Community Edition installed, as well ReSharper. Since we use ReSharper for code analysis, we deactivated Studio code analysis by .editorconfig with only 2 lines:
root = true
dotnet_analyzer_diagnostic.severity = none
Everything worked fine (and still does on another PC).
Now I got a new PC, installed Win 10 from scratch, as well Studio and ReSharper. Now Visual Studio always does code analysis and comments/suggests several issues. Even if I reconfigure issues severity to None, I do not get any changes to my .editorconfig, but still analysing the code.
How can I get rid of Studio code analysis?
This is not a direct answer to your question, but take a look at this article. It describes a way to disable Roslyn-based Visual Studio features through the project properties used by Visual Studio design-time builds. This approach significantly improves memory usage on large solutions.
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 have created data access layer ,Business access layer and web api as separate projects in one visual studio solution.
I am trying to implement angular 4 project using angular cli. Is it better for me to include angular 4 as a class library project and add to the existing solution or do I avoid adding it to the solution and just use visual studio code to open it.
I need to know which is the better code editor to use as far as angular 4 is concerned.
I would argue that nowadays both VS Code and Visual Studio 2017 offer similar experiences. You can check my blog post here for more information:
https://blogs.msdn.microsoft.com/wael-kdouh/2017/09/05/should-i-use-visual-studio-2017-or-vs-code-for-my-next-angular-application/
If you want to successfully use the Angular CLI, the VS Code would be much easier than trying to merge the result into a Visual Studio project.
Alternatively, you can use the new dotnet new angular and use Visual Studio's template. See this link for more information: https://dotnetcore.gaprogman.com/2017/04/20/dotnet-new-angular-single-page-application-setup-and-how-the-template-works/
Most devs I know are going with option 1 and using the CLI and VS Code for the Angular piece and Visual Studio for the back-end piece.
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.
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.