Rapid access to 12 Hive and stsadm.exe

Every SharePoint developer needs to have quick access to the 12 Hive, 12Hive/Bin for the stsadm for various purposes in our daily development work. But, I have seen many of them never try to make this process easier. Even though this is a trivial issue, sometimes its pretty annoying. So here are a few ways to avoid those annoying moments.
(*12 Hive = C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\)

1. Add a shortcut link to the 12 Hive folder in the task bar.Just open the windows explorer and navigate to 12 Hive. Drag the left top corner icon and drop it on the task bar in the right corner. The end result is as follows:

2. Create a shortcut to the command prompt and set the default directory to the 12 Hive’s BIN directory. Add that shortcut to the quick launch bar so that it would be one click away. Even better, you can set shortcut key to open up the command prompt. Set the Target, Start in properties as following:
Shortcut to 12 Hive/BIN

3. Add the 12 Hive to your “Favorites” in the explorer window.

4. To have access to stsadm.exe command irrespective of the folder you are in. Update the “Path” environment variable to add the path to the 12 Hive/BIN folder. (Right click My Computer – Go to Advanced Tab – Click Environment Variable , under system variables, edit Path variable and append the 12Bin path using semicolon as a delimiter).

access stsadm.exe everywhere

5. This is yet another good one posted by Daniel in the comments:

“I usually create a junction point (officially a ntfs reparse point) in the file system using the junction tool from sysinternals (http://technet.microsoft.com/en-us/sysinternals/bb896768.aspx)

junction.exe c:\wss “C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\”

That gives me something like c:\wss pointing to the 12 hive and stsadm.exe under c:\wss\bin.

(I do the same for the Windows Debugging tools and create a junction for them under c:\Debug.)”

If you have any more options to make a developers life even more better and easier, please add to the comments.

7 Responses

  1. I usually create a junction point (officially a ntfs reparse point) in the file system using the junction tool from sysinternals (http://technet.microsoft.com/en-us/sysinternals/bb896768.aspx)

    junction.exe c:\wss “C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\”

    That gives me something like c:\wss pointing to the 12 hive and stsadm.exe under c:\wss\bin.

    (I do the same for the Windows Debugging tools and create a junction for them under c:\Debug.)

  2. Daniel, that sounds interesting. It sounds similar to the symbolic links in UNIX system. Thanks for the idea.

  3. Never heard/knew about junctions points until now. Great tip!

  4. I’ve always just created a fake shortcut – although I like the Path route as well.

    http://weblogs.asp.net/danlewis/archive/2007/11/17/shortcut-to-stsadm-exe.aspx

  5. […] There are tips and tricks that you may want to include for your developers, for instance Andrew Connell’s suggestions and an interesting use of junction points from the Share Notes blog. […]

  6. Point #2 worked perfectly. I hated changing all the way to the bin directory manually. this tip saves me SO much time. Thank you.

  7. […] previously posted this as comments here and here) November 27th, 2009 | Tags: SharePoint; Utilities | Category: Productivity, SharePoint, […]

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: