Sort and Remove Unused Usings in Visual Studio 2008
When I first starting developing in .Net, I had been a Java programmer for many years. I remember when I first started the transition, a long-time VB developer told me how much I was going to *love* Visual Studio. It was as if programming Java in Eclipse was akin to living in the stone age and he had suddenly granted me the programming gift equivalent to fire. "Here you go ... but use this power wisely. With great power, comes great responsibility." Hey, it's not like I was using vi on an terminal emulator! (by the way, have you seen any old school guys program in vi (and still choose to do it)? It's *scary* how fast they are.)
Anyway, it's 2004 and I start my era as a .Net developer using Visual Studio. Dare I say, I actually begin to *miss* some things that were in Eclipse.
Example - In Java, you have "import" statements at the top of every class you write. They are very similar to "using" declarations at the top of a C# class. They basically tell the compiler what packages (i.e. namespaces in .Net) you need to compile the class. Whereas in .Net you only can include an entire namespace, in Java you have the ability to import an entire package:
import java.util.*;
or individual classes within a package without having to import the entire package:
import java.util.Calendar;
import java.util.Date;
import java.util.List;
Flash back to circa 2002 or so. I was working on a J2EE project with a team of developers. Another developer and I were working on a couple of the same files. After he checked a file in and I was going to work on it, I would do a diff on the file to see what he had changed. I noticed every time he checked a file in, along with the changes he had made, he would rearrange the import statements. Now, the usual ordering of imports in a java class are that all the java.* classes go first, then the javax.*, followed by any org.*, and finally your application classes last. The project we were working on was for the state of Georgia, so some of our application packages started with gov.*. Well, he would always move those imports above the java.* packages. I would move them back to the bottom (where they actually belonged). When he checked it back in, they would be right back at the top. I thought to myself, "Man, this guy must be really anal to go through the effort of expanding out and ordering all the imports statements that way. I wonder why."
One day I finally asked him about it. "Why do you re-order the imports statements every time you check a file in and put the gov ones first?" He looked at me with a puzzled look. "Huh?" Then he realized what was happening. "Oh, I just hit Ctrl-Shift-O every time before I save a file to organize the imports." And he showed it to me. In Eclipse, you could use that keyboard shortcut (or access it through the menu) to automatically figure out your individual class imports and arrange them via a configuration of your choice (since he hadn't set up the gov ones in any order, it defaulted them to be first alphabetically).
Wow! Pretty cool! This was 6 years ago mind you. So I got in the habit every time I saved a file: Ctrl-Shift-O, Ctrl-S ... Ctrl-Shift-O, Ctrl-S ... Ctrl-Shift-O, Ctrl-S. I quickly became a "creature of habit".
Back to starting out in Visual Studio in 2004 ... Let's see, I'd like to organize my using declarations. Ok, Ctrl-Shift-O doesn't do that. Hmm ... I wonder where that setting *is* in Visual Studio ... Looks of looking, lots of googling ... Nothing. Well, damn. That kinda sucks. You mean I actually have to manage this myself?!?!? I think to myself, "Am I the only one out there who is wanting this sort of thing???"
Time passes, I am surviving by organizing my usings by hand (barely). The more and more .Net blogs I read, I start hearing about people using and loving ReSharper. Last year, after going solo and starting my own company, I finally decided to pull the trigger and buy myself a copy. And boy, was I glad I did! Along with a bunch of other great things, I notice that it let's you sort and remove unused usings. "There it is, there it is!!!" Ctrl-Alt-O! Organize and remove usings!
Last year, Visual Studio 2008 comes out, but damn - ReSharper is not quite ready for it. Well, work still needs to get done so I need to carry on, albeit without ReSharper for the time being. I am playing around with Visual Studio 2008, and I notice a new menu option under Edit->Intellisense. Whoa, what's this? "Organize Usings". I click on it, and lo and behold, there it is - three options: 1) Remove Unused Usings; 2) Sort Usings; 3) Remove and Sort. Finally!!!
There is no native keyboard shortcut mapped to the "Remove and Sort". Well, we can change that easily enough:
There, I've mapped Ctrl-Alt-O to Remove and Sort. I'm back baby! Ctrl-Alt-O, Ctrl-S! Let's see it in action ...
Before:
And after:
The bottom line is - yes, Visual Studio is a great IDE. But don't fool yourselves .Net developers. Eclipse, IntelliJ, and even NetBeans (my preferred IDE for working in Ruby) are all very strong IDEs that in reality actually do some things (gasp!) *better* than Visual Studio.
Saturday, May 03, 2008 2:52:09 PM (Eastern Standard Time, UTC-05:00) 
.Net | Eclipse | Java | ReSharper | Visual Studio