All the Visual Studio 2010 Keyboard bindings are available here for you to download. These are very helpful resources for a person who spends most of his days in Visual Studio.
http://www.microsoft.com/downloads/en/details.aspx?displaylang=en&FamilyID=92ced922-d505-457a-8c9c-84036160639f
I personally like Ctrl+. which allows me to add the using statement without going to the top of the file. I use it quite frequently.
Showing posts with label Visual Studio 2010. Show all posts
Showing posts with label Visual Studio 2010. Show all posts
Saturday, October 9, 2010
Sunday, September 19, 2010
VS2010 Performance and Bad Video Drivers/Hardware - Redux
Video Driver Bug
Since Visual Studio 2010 is shipped, we continued to have a small but notable series of problem about performance that we've been able to attribute to bugs in video drivers and GPUs.
The issue first came up back during VS 2010 beta in October of 2009. Old, buggy drivers are the usual cause, some newer drivers and GPUs aren't as good at supporting VS's UI as we'd like.
Fortunately, the software rendering inside WPF is pretty good, so the easy fix here is to force WPF to ignore the GPU and use software rendering (WPF's software rendering is actually slightly faster than GPU based rendering on high end CPU with a mid-range graphics card - your mileage may vary).
But first, if you're seeing slow / broken screen updates you should verify you have the latest display drivers for your system. (See "Guidelines for troubleshooting graphics issues in WPF applications" for more information.)
If that doesn't fix it, then there are three ways to force WPF to use software rendering.
First and preferred, the final RTM version of VS2010 includes a UI for forcing hardware rendering off - for just VS. With VS2010 open, go to Tools | Options, then select Environment | General (as shown below). Then uncheck "Automatically adjust visual experience..." and "Use hardware graphics acceleration..."
Second, you can force software rendering mode for ALL WPF applications (including VS) by changing one registry key:
[HKEY_CURRENT_USER\Software\Microsoft\Avalon.Graphics]
"DisableHWAcceleration"=dword:00000001
Note that this key probably won't exist, and you'll probably need to create it. To turn hardware acceleration back on, just change the "1" to a "0".
Third, you can often adjust the hardware acceleration options from the display control panel. However, we don't recommend this option as it impacts the entire machine, the details vary by manufacturer, and the exact impact of all the different options is untested.
It should work this way.
Source: MSDN blog
Since Visual Studio 2010 is shipped, we continued to have a small but notable series of problem about performance that we've been able to attribute to bugs in video drivers and GPUs.
The issue first came up back during VS 2010 beta in October of 2009. Old, buggy drivers are the usual cause, some newer drivers and GPUs aren't as good at supporting VS's UI as we'd like.
Fortunately, the software rendering inside WPF is pretty good, so the easy fix here is to force WPF to ignore the GPU and use software rendering (WPF's software rendering is actually slightly faster than GPU based rendering on high end CPU with a mid-range graphics card - your mileage may vary).
But first, if you're seeing slow / broken screen updates you should verify you have the latest display drivers for your system. (See "Guidelines for troubleshooting graphics issues in WPF applications" for more information.)
If that doesn't fix it, then there are three ways to force WPF to use software rendering.
First and preferred, the final RTM version of VS2010 includes a UI for forcing hardware rendering off - for just VS. With VS2010 open, go to Tools | Options, then select Environment | General (as shown below). Then uncheck "Automatically adjust visual experience..." and "Use hardware graphics acceleration..."
Second, you can force software rendering mode for ALL WPF applications (including VS) by changing one registry key:
[HKEY_CURRENT_USER\Software\Microsoft\Avalon.Graphics]
"DisableHWAcceleration"=dword:00000001
Note that this key probably won't exist, and you'll probably need to create it. To turn hardware acceleration back on, just change the "1" to a "0".
Third, you can often adjust the hardware acceleration options from the display control panel. However, we don't recommend this option as it impacts the entire machine, the details vary by manufacturer, and the exact impact of all the different options is untested.
It should work this way.
Source: MSDN blog
Tuesday, April 20, 2010
What's new in Visual Studio 2010 and .NET 4
Last week Microsoft had launched many of its products. I am most exciting about Visual Studio 2010. I have heard it had got many new features. Well Microsoft can do many things in 2 years. Let's see what's new in Visual Studio 2010 and how can Visual Studio 2010 is different from other versions
One of the first things to note is that Visual Studio 2010 allows you to write code against multiple versions of the .NET Framework and CLR; this means that, even if you still need to work on .NET 3.X or 2.0 code, you can upgrade from Visual Studio 2008 to Visual Studio 2010 and still be able to work on .NET 3.X applications and .NET 2.0 applications.
Some of the features in Visual Studio 2010 and .NET 4 that look really useful are:
One of the first things to note is that Visual Studio 2010 allows you to write code against multiple versions of the .NET Framework and CLR; this means that, even if you still need to work on .NET 3.X or 2.0 code, you can upgrade from Visual Studio 2008 to Visual Studio 2010 and still be able to work on .NET 3.X applications and .NET 2.0 applications.
Some of the features in Visual Studio 2010 and .NET 4 that look really useful are:
- IntelliTrace, which allows you to “rewind” the application to debug
- Multiple monitor support (it’s about time)
- Vastly improved debugging for parallelism
- Significantly improved support for XAML
- Better support for jQuery and other client-side technologies
- Local Team Foundation Server installations (this is awesome for lone developers or developers in small shops)
- Parallel Extensions Library
- F# built into the system
New Microsoft Visual Studio 2010 and .NET 4.0 Launched
Microsoft had just lanched Visual Studio 2010 and .NET 4.0 last week.
Now you can do more pleasant work in ASP .NET and you don't feel like you are fighting with the system.
Here is official Microsoft Visual Studio 2010 link
Now you can do more pleasant work in ASP .NET and you don't feel like you are fighting with the system.
Here is official Microsoft Visual Studio 2010 link
