Dmitry Sotnikov's view on Cloud, PowerShell, PowerGUI and everything he sees around
Claus Thude Nielsen posted a step by step tutorial on how you can get PowerGUI’s version control system to use Dynamsoft.
Which is very cool because Dynamsoft:
Learn more about Dynamsoft and get the step-by-step tutorial here.
Also, I have previously published similar tutorials on:
Darin posted a quick document describing the major features of the PowerGUI Pro version (which are MobileShell, script version control, and technical support) here.
He provides pretty detailed information on what each of them actually means so it should help you figure out whether you want to download the trial of the Pro version (which I obviously highly recommend) or stick to the free version (by the way, they can run side-by-side).
Download the PowerGUI Pro Technical Brief here (registration required.)
I’ve already blogged about the use of PowerGUI Pro Script Editor with Team Foundation Server (TFS), now it’s time to check out integration with another popular source control solution – Subversion.
As with any other revision control system, to integrate PowerGUI needs you to install an MSSCCI provider for the system (this is the API which Microsoft Visual Studio is using). For Subversion there is a bunch of clients available – so use whichever you like as long as MSSCCI is one of its features.
For this post I used TamTam SVN SCC. It seems to be a great client however you would need to pay the author $14.99 unless you enjoy seeing their “Buy now” prompts every few minutes. 😉
(If you really want to save the $14.99 there is also a free SCC client for Subversion: TortoiseSVN – however, you would have to spend a few minutes to make it work because the SCC provider is only supported by a fairly old version of the client – 1.3.5. If you want to go that route, download version 1.3.5 of the client here, and install it along with the TortoiseSVNSCC provider found in Documents & Files section here. You might also have to apply some registry keys on Vista and later.)
Anyway, I went the easy way:
1. Downloaded and installed Subversion v1.4.3 and TamTam SVN SCC .
2. In PowerGUI Pro Script Editor, went to Tools / Options / Version Control, selected TamTam as the Current provider and browsed to the svn.exe file.
3. Now I can add files to Subversion, check out, check in, and so on by using the Version Control menu in the editor:
PowerGUI Pro Script Editor 2.0 integrates with multiple source control systems. In this blog post I will guide you through setting it up to work with Microsoft Visual Studio Team Foundation Server.
First of all, the machine on which you are doing your script development needs to have the following prerequisites from Microsoft:
Now you are ready to start using TFS inside PowerGUI!
Once you’ve done that checking in your scripts is trivial. When you save a script, you will be prompted whether you want to add it to the source control project:
And if you click Yes you will be able to pick the TFS server and project:
And then supply your check-in comments:
After that the Tab displaying the script will have a blue check indicating that the file is under source control, and you will be able to use Version Control menu or toolbar to check in/check out the file and perform other source-control-related operations:
One final comment to add, is that if this is a fresh machine and there already exists a TFS project which you want to join and from which you want to download all existing files, you may do so using the Visual Studio or Visual Studio Team Explorer. All you need to do is add the server/project in File / Source Control / Open from Source Control menu, then double-clicking Source Control in Team Explorer, and Getting Latest Version of the projects you need:
I hope this makes your scripting even safer and more compliant with your corporate policies.
If you are a Microsoft MVP, software vendor integrating with PowerGUI or a trainer using PowerGUI in your classes you can get a free Not For Resale (NFR) license for PowerGUI Pro (our commercial version which includes version control integration and MobileShell).
MVPs can request the license by filling out this form. ISVs and trainers can apply by emailing Darin at Darin-dot-Pendergraft-at-quest-dot-com
Hope this post made some of you real happy. Everyone else can still take consolation in the $99 introductory price at which you can get PowerGUI Pro for the next couple of months.
We are running a special: for the first 60 days on the market PowerGUI Pro – including all the features of PowerGUI freeware plus technical support, version control integration (TFS, Subversion, SourceSafe, StarTeam, etc.) and MobileShell can be bought for just $99 per administrator using the product.
This is a special introductory price, and starting May 1 we will go to regular $199.
I personally think this is a great deal which can make your PowerShell experience way more enjoyable and effective.
Learn more about PowerGUI Pro, download a trial version, and make the purchase at www.quest.com/PowerGUIPro.
The final code and trial keys are now freely available at www.quest.com/PowerGUIPro.
As I mentioned previously, this is essentially the same as free PowerGUI 2.0 available from PowerGUI.org but has version control for PowerShell scripts and MobileShell (PowerShell in a browser including full support for Linux, Mac, iPhone, etc.)
Thanks to everyone who helped beta-test this great release. Give it a try – go to the PowerGUI Pro page, download the final code, get a free trial license, and hopefully buy the product.
Here’s a quick summary of the differences between the free and commercial versions of PowerGUI:
| PowerGUI 2.0 | PowerGUI Pro 2.0 | |
| Administrative Console | Fully functional | Identical to freeware |
| Script Editor and Debugger | Fully functional except version control | Same as PowerGUI plus support for version control systems |
| MobileShell | Not included | Present: Remote PowerShell access from browser and mobile devices |
| Support | Forums | Full commercial support from Quest Software |
| Availability | Available | Currently in beta |
So basically, the freeware version is not going away. Moreover, we keep investing in freeware (as we are now starting to work on PowerGUI 2.1 a big chuck of our investment is going into both versions). What we are doing, is trying to evaluate for new features whether they make more sense in individual administrator/enthusiast scenarios, or more in enterprise setting. This is why MobileShell, version control, and technical support went into the commercial version, and the rest stayed in the free one.
I hope this makes sense. You can hear Darin and I discuss this more in the PowerScripting Podcast published recently.
We are very excited about both versions of the product and their roadmap for 2010!
Subscribe by email
Dmitry's Blog: Cloud, PowerShell and beyond 