Darren McLeod

When I’m refactoring some code if there is an interface change I usually make the interface change first and then fix all the error’s that come up.  Using the mouse to go to the errors window and double click on the next error can get tedious so I did some research to figure out a better way and found there is a keyboard short cut "ctrl-shift-F12" in VS 2008 that will take you to the next error. For more information on keyboard short cuts check this out: http://www.mobydisk.com/softdev/techinfo/dotnetkeyboard.html

The second thing I do( this is the first ) with a new install of Visual Studio is I head over to  http://www.narrange.net/download.aspx  and download the latest version of NArrange.  NArrange is an open source .NET code organizer/formatter/beautifier. After downloading and installing(and noting the folder where the exe is installed) the NArrange setup.msi, I go into my new install of Visual Studio and click on Tools and select External Tools . This opens the External Tools dialogue.  Click Add  and in the Title  field I put "NArrange" and beside the Command  field I click the ... (browse) button and go to the folder where I installed NArrange and select the narrange-console.exe file.  For Arguments  I like to only do one file at a time as I'm working so I set it to $(ItemFileName)$(ItemExt) /b and the Initial directory  to $(ItemDir).  The /b causes a back up of the file before NArrange makes it's changes, thi...