I am experiencing a weird behavior of visual studio 2008 and VS 2010. I had only Visual Studio 2008 on my machine having OS windows Server 2008 R2, at point i did some window layout reset and post that visual studio's window layout is acting strange, it is getting docked or un-docked if i debug a solution. I re-install the visual studio 2008 but problem still exists...Strangely i have newly installed Visual 2010 pro and it seems to have the same issue. I am wondering which system file got corrupted and y it is only with Visual Studios. Please help.
This is normal behavior, actually, for all versions of Visual Studio. There is nothing wrong with your computer or your installation.
Visual Studio has at least two different window layout modes. One of them is the design-time mode, and the other one is the debugging mode.
When you start debugging, the environment switches to the debug mode. In the default configuration, that will cause windows to rearrange themselves (some that were hidden appear, some that were visible disappear, others just change position). into a layout that is deemed "optimal" for debugging code.
The idea is that different window layouts are likely to be optimal for different purposes. In design mode, I might want the Toolbox and Properties windows to be visible. I don't need those at all in debug mode, and would rather devote my screen space to the Immediate, Output, and Auto Variables windows instead.
It can be confusing, because you have to rearrange your windows twice, once for each mode. The good news is that any changes you make will "stick", meaning that they will be saved and re-used each time you enter that mode.
If you really don't like it, just arrange your environment so that it is identical in both modes.
Related: Can I save the window layout in Visual Studio 2010/2012/2013?
Related
When I'm using Visual Studio and I go on the properties window, its really hard to browse for something.
It has this black weird layout which only displays when I'm using dark mode and also gets worse by opening some tabs.
I'm using VS 2015, but this happened to me on VS 2012 that being the reason why I upgraded to VS 2015.
I've tried changing to custom themes to see if it would help but it didn't.
Image of glitch
Dealing with an extremely annoying issue and unable to find a resolution so far around the web.
Issue description:
Using Visual Studio 2019 Community Edition, and after a bit of debugging, stepping through code and inspecting objects in Quick Watch I notice that mouse movement begins to lag. Mouse pointer is still movable but is jumpy, like bad wireless mouse connection. Extremely annoying as I first though wireless mouse was at fault. But the issue goes away immediately after Visual Studio is closed. This is also very reproducible, although does not appear to happen right away, seems to happen after a few debug sessions.
Things I've tried:
Uninstalled all Visual Studio extensions
Reset all Visual Studio settings and performed "Repair" from VS Installer
Disabled Windows Defender, no other anti virus / spyware software is running
Updated Windows 10 to latest update
Updated Visual Studio to latest version as of now
If anyone has any suggestions on how to fix this, please share.
If you are experiencing the same issue, please add details about your environment in comments (Visual Studio edition & update version, .NET version of the project, Windows update version).
enter image description here
This is mainly caused by hardware acceleration feature which is caused by Grafics Card bugs.
The Visual Studio team has continued to notice a small but important series of performance and reliability issues that are caused by bugs in the installed graphics drivers. By default, Visual Studio automatically adjusts the visual experience in order to maximize performance and responsiveness across client configurations. Visual Studio also uses hardware graphics acceleration when it is available on the client. For most customers, these Visual Studio default settings provide the best user experience. However, some users have reported that manual adjustments to these settings can result in improved experience. This article describes how to make these adjustments in Visual Studio.
Solution :
Disable "Use hardware grafics acceleration if available" in visual studio settings (Tooles -> Environment -> General)
enter image description here
I was using VS 2012 in Windows 7. Yesterday, I installed Windows 8 and installed Visual Studio 2013.
And i can not use Ctrl-Shift-V keys for Cycle Clipboard Ring. I have tried to assume manually Ctrl-Shift-V keys for Cycle Clipboard Ring in Tools\Options\Keyboard menu. Still not working.
[SOLVED]- I have tried it in Design Window. It works fine in Code window.
Open up the Visual Studio Keyboard settings and make sure that the binding is setup correctly. You might have accidentally selected a different template the fist time you launched Visual Studio.
In my C# 2005 bindings, it's available. You might have to reset the mapping scheme and restart Visual Studio.
There might be a add-on, like Resharper that's interfering with the keybindings.
The same story on Win7 and VS2013.
In my case helped only removing ReSharper.ReSharper_PasteMultiple shortcut.
Thanks to the thread:
Visual Studio: ctrl+shift+v opens clipboard ring window I've coped with that.
ReSharper had been turned off nonetheless I had to totally remove the ReSharper's shortcut repeatedly pressing "Remove" (it was switching stacked values).
I having the most annoying problem with Visual Studio 2012 settings. Every time I close and re-open Visual Studio I find the Just My Code debugger setting disabled. No matter how many times I enable it, it is always disabled the next time I open the IDE.
Any idea how this could be occurring? All the other settings seem to persist well. It's only the Just My Code setting that's changing.
Well, I found the problem.
I have the .NET Reflector Plug-In installed in Visual Studio and it apparently doesn't like "Just My Code" so it disables it on start up.
I have Visual Studio 20010 Ultimate on Windows 2008 R2 machine. Last week I applied SP1 and after few days I am experiencing UI freeze for some time around 40 to 60 seconds when I save code changes to files.
I have turned off the background compilation, turned off the antivirus still this problem is not going away.
On my 2008 R2 machine I right clicked on the shorcut for VS2010 and selected properties option. In compatability tab I selected to run VS in compatability mode for Windows server 2008 SP1. There is a checkbox and dropdown for this.
For VS 2010 SP1 it is mentioned that it sets software rendering by default. I thought this might be the reason for UI freeze in some case hence I changed the compatibility setting and it seems to be working fine since then!
[With Visual Studio 2012] Try pressing ATL+TAB twice (or switch to another application then switch back to Visual Studio).
That seems to solve the problem.