Monthly Archives: November 2005

Like the Windows XP Power Toy "Open Command Window Here", this utility installs a context menu item into the Windows Explorer context menu for drives and folders.  The install is a very simple affair.  It verifies that you have MSH installed … Continue reading →

Assuming you have VS 2005 installed, just add the following to your profile:   # ———————————————————————# Configure the environment to build under VS 2005 / .NET 2.0# ———————————————————————$env:VSINSTALLDIR="${env:ProgramFiles}\Microsoft Visual Studio 8"$env:VCINSTALLDIR="${env:ProgramFiles}\Microsoft Visual Studio 8\VC"$env:DevEnvDir="${env:VSINSTALLDIR}\Common7\IDE"$env:FrameworkSDKDir="${env:VSINSTALLDIR}\SDK\v2.0"   $FrameworkPath=    [Runtime.InteropServices.RuntimeEnvironment]::GetRuntimeDirectory()$env:FrameworkDir=$(parse-path $FrameworkPath -Parent)$env:FrameworkVersion=$(parse-path $FrameworkPath … Continue reading →

Monad is the codename for Microsoft’s new command shell that is currently in beta.  Monad was coined by Gottfried Leibniz, a German philosopher, mathemetican and statesman from the 17th century.  One of his philosophical works was called Monadology.  Here’s a brief … Continue reading →

Here’s a script I use to see which processes are hogging memory.  BTW, I tell MSN Desktop Search my whole hard drive so it usually occupies the #1 slot:   function hogs {    get-process | sort PM -des | select … Continue reading →

MSH keeps track of the various commands you execute.  You can view this history using get-history or the alias ghy.  You can invoke a command in history using invoke-history <number> or the alias ihy <number>.  One of the first things … Continue reading →

A feature from Lisp that I really like is the ability to pass code around as data.  One of the very cool aspects of Monad is that you can now easily do this.  That is, code can be placed in storage … Continue reading →

For project development, we have a special set of location aliases and we need the PATH, LIB and INCLUDE environment variables set up to build against VC 8.0 (VS 2005).  We store the project specific configuration in a script file called BuildEnv.msh.  In … Continue reading →

As you experiment with your profile ($Home\My Documents\MSH\Micrsoft.Management.Automation.msh_profile.msh) you quickly get tired of having to fire up a new shell to try your changes.  You can reload your profile easily like so: > . $profile $profile is a MSH variable … Continue reading →