When debugging in Visual Studio 2013, I have a variable that is around 130MB, and hovering over it even by accident causes my entire environment to freeze and I have to restart the debugging.
I want to disable the auto-evaluation on hover (even if it forces me to use watches to peek a value), but couldn't find it anywhere in the settings.
Is there a way to disable this?
Related
In Visual Studio 2022, I often will run into an issue where I am typing a smaller word and, when I press SPACE, VS auto-completes it to something completely unrelated to the context that just happened to be the highest in the IntelliSense suggestion popup. How do I change this behavior to only auto-complete/accept suggestions when you press TAB
Edit > IntelliSense > Switch between automatic and tab-only IntelliSense completion
I remember some time ago I could assign a variable in Immediate Window during debug and when hovering mouse over I could see a tooltip with member values just like when hovering over variables in the code.
Now this feature stopped working in my Visual Studio 2015. Did Microsoft remove this feature in VS2015 or I messed something up? Is there a setting for this somewhere in the menus?
EDIT: Because not everyone is so sure about this feature ever existing, I add a screenshot from Visual Studio 2012 where you can clearly see the tooltips for text typed in Immediate Window (here I use the variable web):
Update:
I test it in different VS version(VS2012/VS2013/VS2015/VS2017), it really has this issue in VS2015 or VS2017. But it has this feature in VS2012 or VS2013.
I report this issue to the product team here:
https://developercommunity.visualstudio.com/content/problem/55570/vs2015vs2017-tooltips-stopped-showing-when-hoverin.html
If possible, you could also share your comment there.
By default, Visual Studio 2012, and others possibly, deletes an enabled breakpoint upon clicking it. This to me feels unnatural because clicking a disabled breakpoint enables it. Why then would a subsequent click delete it? I would expect the opposite, which is disabling the breakpoint, similar behaviour to Xcode.
Is there a setting somewhere that allows me to modify this behaviour, to clicking to toggle between enabled and disabled?
i don't know about a setting to change the single click behavior, but a little experimenting revealed that shift clicking the breakpoint disables instead of deletes it. this is in visual studio 2019. i found your question because i was wondering the same thing.
I have a minor annoyance with Visual Studio. In the bottom right hand corner of Visual Studio, there is a INS/OVR button to toggle Insert/Overwrite. I always have this button set to INS, and I always want it to be set to INS.
However, sometimes when I build the solution, Visual Studio changes this back to OVR. I have to click on the button to change it back to INS, which is slightly inconvenient.
I do not know why this setting sometimes changes.
Is there anyway I can permanently disable the overwrite mode in Visual Studio or prevent solution builds from changing this setting?
Visual Studio, Tools > Options > Environment > Keyboard, remove the shortcut binding for Edit.OvertypeMode
I don't think you can permanently turn insert/overwrite off. Are you accidentally pressing insert on your keyboard? You can press the insert key on your keyboard or Shift+0 on the numpad to toggle it back again.
Go to Visual Studio Code's settings and type "overtype" in the search bar, and set it to 'never'.
Hope this helped! :)
Sometimes visual studio wont disable overtype even if you hit insert with numlock on, If this happens just close script and open it again and it will work. This is a bug in visual studio.
Is there any way to disable VA X when launching VS and turn it back on only when needed? Since it will cause some lag. I seem can't find the option either in VS's option or VA's option.
Hold the shift key down when Visual Studio starts up - this will prevent all addins from loading (at least in more recent versions of Visual Studio).
In VS2013,
On the Tools menu, click Extensions and Updates.
In the Extensions and Updates dialog box, locate Visual Assist.
Disable it.
Visual Assist has a command to disable its features; Enable/Disable is located on the Visual Assist menu. You could run that command (for example via a macro) at startup, then re-enable when you wanted to you use its features. However, you can't do this at the same time as preventing it from loading.