I am an administrator that is, to be quite honest, infatuated with PowerShell. I have done some minor coding in my past; mostly using Perl and XML for repetitive administrative functions. With the introduction of PowerShell v2, I started playing around with creating simple scripts to do some of my daily tasks. I then attended The PowerShell Saturday event in Charlotte, NC last year and was able to see some of the things that PowerShell v3 can do. Well, let’s just say the infatuation became an obsession. I still am not a ‘coder’ but have written and posted a few blogs which included scripts that I found very helpful.
I was previously using PowerGUI but when I upgraded to PowerShell v3 I started having problems and did not feel like trying to figure it out since the PowerShell ISE that is included with version 3 is quite good. I was quickly able to get the hang of using the ISE to step through my scripts for debugging and logic and was quite proud of myself. I remembered seeing that Sapien was one of the sponsors of PowerShell Saturday so I decided to take a look at what they offered. I found PowerShell Studio 2012 and downloaded a trial version. I then contacted the company since Sapien is one of many companies that have partnered with Microsoft to offer products to MVPs.
Being an administrator, it took me a little while to get used to the development interface. It reminds me of the layout that Visual Studio uses. I had been fighting with debugging a PowerShell script that requires version 2. I had tried both PowerGUI and PowerShell ISE to help debug the application so that it would run on my laptop that has version 3.0 installed. Using the –version 2 switch did not resolve the issue. Once the form was created, the application would loop until it crashed. Enter PowerShell Studio 2012 and the powerful Debug File option. I was able to use this functionality to see that specific line of code that was causing the problem. I remarked out that single line of code, and Viola my application works again. This would not be a big deal, but the guy that wrote the application does not work with me anymore so I did not want to reach out to him to ‘fix’ it for me.
Here sits a happy MVP that is loving using PowerShell Studio 2012 and learning more and more each day. Take a look at what they have to offer. I am sure you will be as happy with the product as I am.