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.
Related
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've created an Umbraco 7.1.8 in Visual Studio 2013 using MVC templates. When I edit the templates in Visual Studio the editor slows right down and VS shows a permanent 13% usage in Task Manager. If it helps, I'm using Windows 8.1 64-bit on a machine with a 2.3GHz quad-core cpu. Other projects work fine.
Any help/suggestions would be appreciated.
Jason
Okay, found out what the problem was. It turns out if you don't include the .cshtml file in your Visual Studio project (just edit it with Show All Files enabled), you don't get Intellisense and it results in the CPU usage and performance issue I described.
So basically, if you're editing files in Visual Studio, make sure they're included in the project (not greyed out in the Solution Explorer). I'll accept this as the answer as soon as it lets me.
I'm considering using VS2012 RC to put together coded UI tests (since VS2010 SP2 FP2 does not fully support IE9).
Currently, my test projects are contained within a solution which is connected to our TFS team project. I also set up a build definition to build the project when new code is checked in (the builds are performed on our build machine).
I suppose that if I upgrade my solution to VS2012, then to be able to build the solution on the build machine I will need VS2012 RC installed there too, right? But then is it possible to specify in my build definition for my project to be built by VS2012 instead of VS2010?
Is it possible for me to upgrade my project with VS2012 while still using TFS2010? I should note my solution will be the only one upgraded to VS2012. All the other solutions in the company still need to be built by VS2010. A company-wide upgrade to VS2012 won't be in place for at least a few months, I imagine.
Or do I need a separate build machine or anything?
Any thoughts, ideas or solutions appreciated!
UPDATE: So I gave it a try, and everything worked okay. My only problem is that the Coded UI tests I have didn't work after being re-built on on my build machine, but I suppose that's probably something I'd need to ask about elsewhere. To clarify, the solution built successfully, but the tests still failed.
Visual Studio 2012's project changes allow most types to still be opened by Visual Studio 2010 with SP1, so it depends on what kind of projects are in your solution - see this page for the full compatibility list:
If you created your assets in Visual Studio 2010 with Service Pack 1
(SP1), many of them will load and run in Visual Studio 2012 without
any further action on your part. Many assets will also open again in
Visual Studio 2010 with SP1 without any issues, even after you open
those assets in Visual Studio 2012.
See also "Round-tripping with Visual Studio 11" on the VS blog which has more detail.
Note though that if your build process uses custom build activities then just installing Visual Studio 2012 breaks the build definition on your local machine, and also that MVC1 or MVC2 projects just aren't supported by VS2012. Oh, and Visual Studio 2012 isn't a RC any more, it was RTM'd last week.
(I presume you mean 2012 RTM rather than RC, now that the final release is available)
Theoretically (from what I've read) VS2012 and VS2010 use the same project/solution file format, so you should be able to switch between them without any compatibility issues (aside, presumably from obvious things like creating new file types that VS2010 doesn't understand)
TFS updates have historically been backwards compatible, so you can usually use different client and server versions (but usually you need a compatibility pack installed for old clients on new servers, a new client running against an old server has usualyl been fine). So I'd expect this to work well.
I'd say try it, but diff any files that appear in VCS2012's Pending Changes carefully before you check in to be sure that it hasn't changed anything that will cause problems. The worst that can happen then is that your development machine gets a "corrupt" version of the code and you'll need to revert to 2010.
(This is the approach I've been using with our 130-project C# solution, and so far (1 day) it's working fine, apart from the new UI making my eyes bleed as they try to find the information in all the indistinguishable monochrome clutter)
I'm looking to extend the source control of Visual Studio 2010 Team System. I need to halt the check-in process and pop-up a little GUI to do some things. I've found this; http://msdn.microsoft.com/en-us/library/ms182075(VS.100).aspx, does anybody have any good tutorials or similar lying around i'd appreciate it.
Your best bet is a check-in policy. If you download and install the latest VS 2008 SDK, you can re-compile the check-in sample in VS 2010 after fixing up the assembly references. We'll be publishing update SDK samples when Beta 2 is released.
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.