This week, Microsoft announced Monad’s product name, PowerShell, as well as releasing an RC1 release (The very good user guide can be found here). There are quite a few changes that you can read about on their new blog: http://blogs.msdn.com/powershell. While I think Monad is just fine for a name, I like PowerShell, too. It’s much better than the other names these dummy marketers came up with. I actually have this image in my head when I think the name PowerShell that I might just blog about, but not in this post. While we’re still on naming, though, msh is a way better name for a file extension that ps1. Oh well.
Because of the name change, the profile folder in My Documents has changed but not to something intuitive, so I figured I’d post about it and hopefully let Google pick it up. The folder name for the betas was My Documents\msh. In this folder, you could put your profile script to customize the shell as well as other scripts. I posted earlier about setting the Visual Studio environment variables via script (btw, I plan on making that script better, stay tuned). That’s where you’d put those scripts.
Since the name change to PowerShell, it’d be natural to think that the folder would have to be renamed from msh to ps1, or ps. You’ll find that that is totally wrong. I think for the same reason that the .msh extension got changed to .ps1, instead of just .ps, the new folder name is My Documents\PSConfiguration.
You’ll also have to rename all of your scripts to .ps1. I tried to come up a quick little command, but I failed and just did it by hand (I only had three). I’m still stuck in the learning curve. Luckily, Peter Provost, who is far more proficient in the new shell, gives us just what we need.
Technorati tags: Monad, PowerShell, MSH
Now playing: Matthew Sweet – Sick Of Myself
test test test
blah blah balh