This bug report on Microsoft Connect suggests symptoms similar to those you describe The simple fix might be to turn off the "rich client visual experience To do that, follow these steps: From the "Tools" menu, select "Options Expand the "Environment" category, and select "General Uncheck the box labeled "Automatically adjust visual experience based on client performance Uncheck the box labeled "Enable rich client visual experience You might also try turning off "Use hardware graphics acceleration if available Click OK I realize this isn't a particularly good long-term solution, but it might help to make Visual Studio usable for you. There are still some problems like this that crop up since they switched the user interface to WPF. It's really difficult to justify switching client applications to WPF if they can't get it quite right in their flagship development software Of course, a lot of things were significantly improved from the beta versions to the RTM—fonts in the editor window were the big one although they're still not exactly the same in VS 2010 as they were in previous versions.It appears that certain client configurations can still cause strange bugs like this one to appear.
For what it's worth, I've never personally experienced this on any of the several different machines I run VS on.
This bug report on Microsoft Connect suggests symptoms similar to those you describe. The simple fix might be to turn off the "rich client visual experience". To do that, follow these steps: From the "Tools" menu, select "Options".
Expand the "Environment" category, and select "General". Uncheck the box labeled "Automatically adjust visual experience based on client performance". Uncheck the box labeled "Enable rich client visual experience".
You might also try turning off "Use hardware graphics acceleration if available". Click OK. I realize this isn't a particularly good long-term solution, but it might help to make Visual Studio usable for you.
There are still some problems like this that crop up since they switched the user interface to WPF. It's really difficult to justify switching client applications to WPF if they can't get it quite right in their flagship development software. Of course, a lot of things were significantly improved from the beta versions to the RTM—fonts in the editor window were the big one, although they're still not exactly the same in VS 2010 as they were in previous versions.It appears that certain client configurations can still cause strange bugs like this one to appear.
For what it's worth, I've never personally experienced this on any of the several different machines I run VS on.
Thanks so much, turning off hardware acceleration fixed it for me. – Joey Apr 10 at 7:40 Fantastic answer to what seemed like a phony question. I'm impressed!
– anon Apr 12 at 2:23.
I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.