@joeman42
You can do things in PowerShell with a fraction of the code it takes in VB, especially if you get in the habit of making your functions be pipeline functions. The scripting language itself is like only 15 keywords vs, VB's 130 or so. You don't need any more than the 15 key words, because of the power of accessing everything as an object, the power of the pipelining, and being able to access .NET objects. Also, anything you do in a script can be done in realtime in the shell... so you can test bits of code as you go.
It's actually superior to Bash scripting, IMO. It's Bash scripting on steroids (for Windows).