About the author

Steven Harmansteven harman :: makes sweet software with computers!

For recent posts and more about me, scroll to the bottom.

Subscribe

  • Subscribe to my feed. via RSS
  • Subscribe via email via email

News

Badges

  • Subtext Project
  • Support Subtext

Some Small Ways to Reduce Daily Development Friction

Brennan recently posted a great tip for changing the RSS Feeds that Visual Studio displays on the Startup page. Finally I can get rid of those horrible Microsoft articles and get some good content in that window!

I quickly realized that many VS users probably already knew about this, but to many others, self included, this was totally new. And what's more, it's useful!

So with that in mind, I decided I would start sharing some simple tips, tricks, and shortcuts that I use within the VS IDE and Windows environment to reduce the friction of many day-to-day development tasks.

Open Containing Folder

Open Containing Folder - Context menu Within the Visual Studio IDE, right-click on a file's tab and select the Open Containing Folder context item. This will launch a new Windows Explorer window and navigate directly to the file's directory in the file system.

This is very useful if you're a Subversion + TortoiseSVN user as it will allow you to quicly access all of the TortoiseSVN context menus for the file. It's also great for doing merges, diffs, etc...

On a related note: If you are a TortoiseSVN type of guy (or gal), you might want to check out VisualSVN. This is a great little VS plugin that brings all the goodness of TortoiseSVN right into the IDE. Talk about zero-friction! Do keep in mind that VisualSVN is not free (as in beer nor speech).

Open Command Window Here

Open Command Window Here Another great context-menu trick that I use is the Open Command Window Here command for Windows Explorer. This menu item will launch a new terminal command prompt and automatically navigate to the directory you right-clicked on.

Clear as mud? Let's walk through a quick example just to be sure.

Running in the command prompt Say that I'm in the Subtext source code and I'm working with the Installation SQL scripts. Now let's pretend I want to run some commands from the command prompt against some of the files within the Installation Scripts directory (as pictured above).

To quickly launch a command prompt directly into that scripts directory I only need to SHIFT + right-click on the Scripts directory from Windows Explorer, and then select the Open Command Window Here context item. Now I'm ready to start executing commands without having to navigate through the file structure by issuing a bunch of cd commands. This is especially useful if, like me, you tend to keep an Explorer window open to the files you're currently working on.

More to come

As I said in the start, these tips aren't meant to be ground-breaking and process changing in caliber. They are just small things that help me get my work done... and reduce friction along the way. I intend to post more articles like this in the future as I discover little gems that boost my productivity.

If you have more tips, tricks, shortcuts, etc... please share! It's all about the community effort. :)

What others are saying.

# re: Some Small Ways to Reduce Daily Development Friction
Gravatar earljon
Jun 19, 2007
On the Command Window context part, some of us don't already have this but one can manually add a context menu for command prompt by following simple steps:

1. On Windows Explorer, Tools/Folder Options.
2. Click the tab File Types.
3. Find the File Type "Folder" and click the Advanced button.
4. Click the New button, and type "Open Command Window Here" (no quotes) on the Action text box and type "cmd.exe" as the application that will perform.
5. Close all the windows and new context menu is created.

I only tested this method on my WinXP box.
# re: Some Small Ways to Reduce Daily Development Friction
Gravatar Steve Harman
Jun 19, 2007
@earljon: Good point!

I totally forgot that the Open Command Window Here functionality was only available (as a built-in OS feature) for Windows Vista.

Sorry about that... I didn't mean to leave the the non-Vista folks out in the cold. So thanks a ton for the tip on enabling this for WinXP!
# Some Small Ways to Reduce Daily Development Friction
Gravatar DotNetKicks.com
Jun 19, 2007
You've been kicked (a good thing) - Trackback from DotNetKicks.com
# Tip: Get Vista's
Gravatar Jerome's TOT
Jun 20, 2007
Tip: Get Vista's
# re: Some Small Ways to Reduce Daily Development Friction
Gravatar jrummell
Jun 21, 2007
XP users can also use the Open Command Window Here powertoy available at http://www.microsoft.com/windowsxp/downloads/powertoys/xppowertoys.mspx.
# re: Some Small Ways to Reduce Daily Development Friction
Gravatar John S.
Jun 21, 2007
Have you heard of CoolCommands? It adds some nice context menu options for the solution explorer.
# re: Some Small Ways to Reduce Daily Development Friction
Gravatar Steve Harman
Jun 21, 2007
@jrmmell: Thanks for the link! While my main dev box is Vista, I still have several client-specific VM Images that have XP, so this will no doubt be useful there.

@John S.: I'll have to give CoolCommands a whirl. I think the Locate in Solution Explorer, Collapse All Project, and Resolve Project References look like they could really reduce some more of that friction we feel in the daily grind.

Thanks!
# Links (6/21/2007)
Gravatar Member Blogs
Jun 21, 2007
.NET ARCast.TV - Presenter First Pattern (Part 3) SubSonic: New Query Engine In The Works How to sort
# re: Some Small Ways to Reduce Daily Development Friction
Gravatar Scott
Jun 22, 2007
Have you tried AnkhSvn? It's free like beer and speech (Apache license). Great VS subversion integration...
# re: Some Small Ways to Reduce Daily Development Friction
Gravatar Steve Harman
Jun 22, 2007
@Scott: I have used AnkhSvn before, but I didn't like it as much as I do VisualSVN.

AnkhSvn seemed to have problems working with Resharper - especially when it comes to renaming files. It also seemed to increase project startup time by a noticeable amount (like an extra 15-30 seconds).

Granted, I've not tried AnkhSvn in about six months, so the new versions very well may have addressed these issues.

In the end, I think I like VisualSvn because it works just like TortoiseSVN, but inside of Visual Studio. But who knows... maybe I'll give AnkhSvn another whirl - could make for a good blog post.
# re: Some Small Ways to Reduce Daily Development Friction
Gravatar bob
Oct 14, 2007
this is very stupid
# re: Some Small Ways to Reduce Daily Development Friction
Gravatar kalissa grant
May 14, 2008
you don't give notes on ways to reduce friction you edeot
Comments have been closed on this topic.