The source control system, whatever it is must be integrated with PowerGUI as that is my editor of choice.As I sat down to figure out what my solution would look like, I identified the following requirements: I was familiar with the concept of Source Control from the likes of Team Foundation Server but had never looked into it. How did I keep track of all of the changes in a script of this length? My current record for example is a 387 line script. You can read more about PowerGUI by checking out Dmitry's excellent blog HERE.As my knowledge of Powershell has increased, so too has the length and complexity of the scripts I create. But Dmitry and Quest Software got it and produced PowerGUI. The visual imagery of that one is precious!).
(10,000 thanks to Paul Madden for introducing me to that wonderful phrase. When I first started telling people about Object Pipelines, ObjectFlow engines, and Know-Nothing Utilities - people looked at me like I had a rat's tail hanging out of my mouth. Dmitry Sotnikov and the guys at Quest really got where we were going with PowerShell and PowerGUI does a great job exploiting PowerShell's capabilities. PowerGUI ROCKS! If you haven't used it yet, you should download it (it's free) and kick the tires. Yesterday was the official launch of Window Server 2008, the first version of Windows to include PowerShell! Is that a good day or what? How could the day get any better? Well, the people at Quest Software answered that question by officially releasing PowerGUI!
0 kommentar(er)
