Learn about Windows PowerShell
Today’s Beginner Event 10 was really easy. It was troubleshooting. I have gotten pretty good at troubleshooting these last few weeks because I have a hard time making my scripts run correctly the first time. It seems that I write code, click Run to see what is going on, and fix the errors. I used to do accounting work, and I love looking for inconsistencies and typographical errors. Writing a Windows PowerShell script seems to be broken into three parts: Figure out how to do something, try to make it work, and look for errors. For the first step, I use MSDN. For the second step, I rely on the Scripting Guys’ sites (the Hey, Scripting Guy! Blog archives; the Official Scripting Guys Forum!; and the Script Repository). The last step is where I think the real fun begins—look for errors. The biggest thing my Script Monkey taught me in all this is to read the error messages. Of course, the trick is to make sure the script shows error messages. There is something you have to turn off in order to make the error messages appear.
While I was out yesterday getting my hair done, I picked up a cordless weed eater and I am anxious to try it out before it gets too hot today. So I will say good bye, and get this e-mailed to Ed so that he can look it over and send it to Craig for editing and posting.
Hope you have an awesome weekend. I know I plan to. Oh, by the way, I have a secret for you: The Script Monkey thinks he is going to spend the weekend out in his woodworking shop. He does not know that I have amassed a huge “honey-do list” for him. I use the to-do list on the calendar for Windows Live, and as you can see in the following image, it will keep him busy for a while. Well, I’ve gotta go.
Microsoft Scripting Guy Ed Wilson here. Today is Day 10 of the 2010 Scripting Games; all the events have been revealed. Keep in mind you still have an entire week plus the weekend to finish your submissions. The judges will continue to grade the scripts, and Craig will continue to update the leaderboard. Check out the due dates page for more information. Let me invite you to continue to keep up with the 2010 Scripting Games by following us on Twitter or Facebook. If you have any questions, send e-mail to us at firstname.lastname@example.org or post your questions on the 2010 Scripting Games Forum. Check back later today for the leaderboard and prize winners. Beginning tomorrow with Weekend Scripter, we will take a break from the Games. We have some really cool scripts we will be examining over the next seven days, so keep in touch.
Ed Wilson and Craig Liebendorfer, Scripting Guys