I'm using Visual Studio Community for Mac (2017), which is different from the one on Windows (it's a "rebranded version of MonoDevelop"). Specifically, I'm using it to write ASP.NET, C#, JS, and CSS but I think the warnings are only for C# code.
Every time I run my code, I am taken from the tab I was just in to another tab where I have a warning. I find this switching extremely disorienting, so I need it to stop.
I don't need or want to fix the problem causing the warning right now. I know I can go to "Options" > "Compiler", then set "Warnings level" to 0, but I don't want to not see a list of the warnings I have.
How can I prevent it from switching my current tab around?
After suffering with this for too long, I finally figured out the solution.
Simply check the checkbox next to the error in the list (in the "error pad"):
It will be shown (at least at first) in strikethrough and it won't steal your tab focus anymore (unless you uncheck it).
You can either do this for every warning or you can go to Preferences (shortcut: command + comma) and set a setting so that they automatically get checked off. The setting is "Build" > "Jump to first error or warning" and I set it to "Error" since I like being taken to any problem that prevents things from compiling. If you want it to never steal your tab focus, you should set it to "Never".
Related
So I didn't use to have this issue as much in older versions, and it even then it was easy to get used to, but i got VS 2019 recently and now when I write code it'll randomly autocomplete half way in and add shit I didn't write WHILE IM STILL WRITING. I don't press enter, I don't click on anything, it'll just add what it thinks I want without any confirmation.
I tried searching how to disable this, but I only ever find how to turn off intellisense recommendations altogether (Tools > Options > Text Editor > C# > IntelliSense). I don't want to disable the completion list from showing up, I WANT intellisense, I just want it to let me code without inserting new code on it's own. Just show me recommendations, don't automatically add them in for me without any input from me.
Edit -> Intellisense -> Switch Between Automatic and Tab-Only IntelliSense Completion
Had the same problem, this worked for me.
I think you want to disable the IntelliCode. you can do it by
Choose Extensions > Manage Extensions, find and select the IntelliCode
extension, and then click Disable
I was running into this same issue with Visual Studio Community using C# and Resharper on a fresh installation.
This seems to occur on writing invalid syntax, Visual Studio replaces whatever is written with it's closest valid guess when the user presses space. Specifically I was typing in a variable without declaring a type first.
output // gets overwritten automatically with XmlOutputMethod
var output // does not get overwritten automatically
Unfortunately, I do not know how to disable this feature in Visual Studio. Hopefully this information is of some use.
I've recorded a short video of my text being overwritten by Visual Studio, which can be found here
I tried following this path the message suggests but there but wasn't able to find "Location" after moving to "Settings". Where is this checkbox?
While it is possible to do that, you should think about whether you want this. Having the wrong PDBs or having the wrong source code may lead you into wrong conclusions about what you're debugging.
You should only activate this if you know about the consequences, and the consequences are:
you cannot really trust what you see
you may make wrong conclusions
you may change source code which is not affected by your bug
if you change code, you may introduce new bugs instead of fixing the bug
With that warning spoken:
In Visual Studio 2019:
Right click the breakpoint
Click on Conditions... or Actions... (It seems that Settings... is no longer available)
Click on the link and change the checkbox
While debugging in Visual Studio v16.3.2 I want to back on the previous breakpoint and I am trying to achieve it via Step Back Over button. Why this button always disabled?
The reason could be that it's disabled in your IDE.
Try
Tools > Options > IntelliTrace > General
and in there make sure that “IntelliTrace events and snapshots” is checked.
This might or might not require a restart of the IDE.
I am not sure if you are using correct configuration but link can help you setting.
Step Back Debugging
Other possible reason could be, is step back allowed on variable assignments?
I want to completely remove "error list" from visual studio 2008, not disable it i want it gone. It annoys me to no end popping up endlessly, i guess i must be "doing it wrong" but w/e i just want to use VS without being alerted every other keystroke about some warning.
I've tried editing many different fields in the options (tools -> options) it has only slightly decreased the frequency of the error list popping up. I have also deselected errors, warnings, and Messages. and it pops up with nothing to display. unpinning it doesn't help either.
also upgrading to VS 2010 is not an option at this point.
Im looking for a solution something like the following: remove a dll or config file responsible for this
Also I still want the inline validation (the little squiggly marks, etc), but
the error list window annoys me.
I think this is probably exactly what you're wanting:
http://blogs.msdn.com/b/zainnab/archive/2010/05/16/hide-or-show-error-list-when-the-build-finishes-with-errors-vstiptool0022.aspx
You can change this behavior by going to Tools -> Options -> Projects
and Solutions -> General and deselecting the "Always show Error List
if build finishes with errors".
I'm guessing this will work with ASP.Net as well, since that's building on the fly.
I am using Visual Studio 2017, and I also have to cope with the useless, impossible-to-disable, annoyingly-in-your-face, and outright disturbing "Error List" window.
So, here is what I did:
Undock the "Error List" window to make it free-floating.
Resize it to the smallest size possible.
Move it out to some remote area of the screen where it is not so annoying.
And voila, problem solved ! (*1)
*1 Well, problem mostly solved. It will be completely solved when I abandon this dinosaur of an IDE.
My 'Error List' was constantly displaying also (VS2012). I also hate it.
I turned it off years ago, but today it just started appearing.
It was being caused a unreadable packages.config file. For some reason that reports it's fail state through the yukky 'Error List'.
Fixing the packages.config file stopped the 'Error List' from appearing.
for VS2017, select the "Build only" value from the drop down list in Error tab. Refer to the image below:
Hope this helps!
On Error tab, you have Errors / Warnings / Info buttons. Click on Errors button (de-press).
hope it helps.
I suggest turning off inline validation.
Yes, I know that you still want it. But, seriously, how important is it? It's trying to validate code that is half-written. How valuable can that be?
First of all, as-you're-typing code validation is distracting. It makes it harder to focus on the problem you are trying to solve. For example, writing a function with a non-void return will display the "not all code paths return a value" error continually until you get to the end of the function. In the meantime, the editor is telling you that there is a problem. I am sure that people learn to ignore these things over time (I have never kept the feature on for more than a few minutes after a new VS installation, so I don't know), but if you are actively ignoring something, then what good is it?
Second of all, any good that the validation would be capable of is unnecessary, because those errors will be brought to your attention at compile-time anyway. Having an uninitialized variable pointed out to you while you are thinking through the algorithm does not improve the quality of the code at all verses having it pointed out when you try to run the program. The variable is still going to be initialized either way. And there is an extremely high likelyhood that you are going to fix the problem before trying to run the code anyway.
So I just don't see the point of it. I suggest turning it off, and then your problem goes away.
UPDATE
As pointed out by #Charlie Kilian, there is a flaw in VS in which .aspx files are not validated at all, unless the "Show live semantic errors" option is enabled for C#, rather than validating those pages at compile-time as would be expected.
Therefore, editing aspx files will require turning this option back on for validation.
I guess I'll be going back-and-forth with it from now on. I hope they fix this in future versions of VS.
I still think that doing a semantic analysis and error-reporting on code that is actively being edited is a fool's errand. (Of course, I have also been known to write entire programs in notepad, just to see if I could get it to compile and run correctly the very first time without the crutch of Intellisense. It feels pretty awesome when it works.)
Selected answer is incorrect because unchecking "Always show Error List if build finishes with errors" does nothing to stop the dreaded Error List window from popping up on other errors, even if you change it to show only Build errors.
11 years later in Visual Studio 2022 it is still impossible to disable Error List window.
The only correct answer to the question "Completely remove error list from visual studio" is to uninstall Visual Studio itself which, thankfully, also removes Error List window.
Either that, or we should all get used to it, because Developer Gods from Microsoft want everyone to work in absolutely the same way as they do. Every workflow that differs from their own is wrong, and every thought that doesn't align with their grand vision is blasphemy.
It is One Microsoft Way or the highway.
I am getting the following error message while running .net 3.5 applciation
Your step-into request resulted in an automatic step-over of a
property or operator.
This behavior can be overridden in the context menu for the line being
executed by choosing 'Step Into Specific' or by unchecking the option
'Step over properties and operators'.
Do you want continue being notified when an automatic step-over
happens?
What does this error message mean?
VS2017 and VS2019:
Tools > Options > Debugging > Uncheck "Step over properties and operators > (Managed only)".
It is not an error message as such. The IDE is telling you that tracing for some of your code is being skipped during debugging due to the current settings. If you want to be able to trace into the code, change the settings as described in the message.
You can change this behavior by going to: Tools -> Option -> Debugging.
The setting for this in VS2010 is under: Tools -> Option -> Debugging (near the middle)
To be more specific: the option to enable in Visual Studio 2010 is:
Tools->Options->Debugging->General->Enable property evaluation and other implicit function calls
As answered by other people this is an informational message from Visual Studio telling you that it could have stepped into a line of code but rather stepped over it due to current dev environment settings.
There are three ways to change this behaviour in VS2012:
Change the settings: Tools->Options->Debugging->General->Step over properties and operators
OR
Right click on the line of code to get the context menu. Then untick: Step over properties and operators
OR
Select 'Step into Specific' in the right click context menu which will ask you which specific function you would like to step into. It will list all the properties/functions involved in the current source line.
In Visual Studio 2013: right click on the line that caused the message to pop-up.
This will bring up the context menu.
Uncheck the option: Step over properties and operators.
Other posts have the correct answer, which state that you can change the option in Tools > Options > Debugging > Step over properties and operators (Managed only) in Visual Studio. I wanted to add an image from the Options dialog for those who are visual. Uncheck the property if you want to perform Step Into (F11) without automatic Step Over (F10).
The reason that we get this prompt is: that we may have created properties or operators in our classes, and when, during debugging, we reach that line of code, it is stepped over (like the effect of F10 ) instead of stepping into ( the actual effect of F11 )
e.g., this line of code,
having pressed F11 here, resulted into effect of pressing F10
So Visual Studio notifies us..and gives this beautiful, well illustrated message, which I could only understand when I read the following blogpost
Credits: AutoStepOver a blog post
The other answers are suffient for turning the feature on or off. Lacking is the insight as to WHY one would want to do one or the other.
For beginning C# programmers their property method is a simple {get,set}. Since this code is not worth viewing we check the box "Step over properties...".
However, when your property settings become more interesting, you may want to step into the property method to ensure it's behavior is correct. Once you tell the IDE "Don't bother me any more", then later when your "step into" fails for a complex property method, now it's your fault.
My recommendation would be either to remember how to switch the option on and off for future debugging sessions or uncheck the "Step over..." setting and learn to toggle between F11 and F10 as appropriate.
Another option is never to use "step into". Just set a breakpoint in the method/property/operator you want to debug and click the step (F10). This way you step into only the methods you are debugging.