Archive for the 'PowerGUI' Category



PowerGUI 2.4 gets a great review by Windows IT Pro magazine

Review of PowerGUI - PowerShell script editor, debugger, custom development environmentIt’s not often that you get an independent product review with summary like this one:

PowerGUI Pro 2.4
PROS: Cost-effective; easy to install and use; removes barriers to implementing in-house PowerShell solutions
CONS: None to speak of
PRICE: $199 per installation
RECOMMENDATION: Get it, and use it. I’ve become addicted to PowerGUI Pro, especially the PowerGUI Script Editor

Yet, this is exactly what Windows IT Pro magazine has just published. And they were reviewing version 2.4 – without all the 3.0 functionality taking PowerGUI to the new level. Saying that I am excited would probably be an understatement.

And this is even better, Ryan Femling from Windows IT Pro was actually actively using the tool – rather than relying on some sort of vendor marketecture (I did not even know this review was in the works) and his review is solely based on his scenarios and applications he found to be important for his work.

Read full review here and I bet there is a good chance that you might learn a couple new things even if you are already an active PowerShell or PowerGUI user!

PowerGUI Editor 2.4 and AD cmdlets 1.4 compatibility issue

[UPDATE] This issue has been fixed in AD cmdlets 1.5.1 – please download the latest version of AD cmdlets here.

We have found a compatibility issue between PowerGUI Script Editor 2.4 and AD cmdlets 1.4 (these are the current versions at the time I am writing this post.)

SYMPTOMS

You execute a script which is using QAD cmdlets. The first time the script executes fine. However when you try to execute it again, the script fails with the “Object reference not set to an instance of an object.” error.

ISSUE

The issue is related to the way QAD cmdlets are handling initialization and unloading of the snapin.

SOLUTION

Set PowerGUI Script Editor to not reset PowerShell runspaces between the debug sessions:
1. Go to Tools / Options / Debug Options,
2. Select the Run all scripts in the same runspace option.
3. Restart PowerGUI Script Editor.

We are sorry for the inconvenience and are working on fixing the issue in the next releases.

Intellisense patch for PowerGUI Script Editor 2.4

If you experience intellisense issues when working with Exchange cmdlets in PowerGUI Script Editor (and by issues I mean that you have the Exchange snapin selected in File / PowerShell Libraries, and cmdlets work in your scripts just fine but intellisense does not appear) – suffer no more, there is now a fix available.

To get the patch simply:

  1. In PowerShell Script Editor, on the Tools menu, click Find Add-Ons Online,
  2. In the dialog box search for ‘fix‘,
  3. Select and Install the PowerGUI 2.4 IntelliSense issue fix (Exchange cmdlets).

 

Get add-ons right in Script Editor

One of my favorite features in PowerGUI 2.4 is the add-on finder in PowerGUI Script Editor.

As you probably know, Script Editor has tons of extremely useful add-ons with great additional features: from script signing to built-in help explorer. However, you used to have to install the add-ons manually – and this was a bit of a hassle. Now, all you need to do is:

1. Go to Tools / Find Add-Ons Online,

2. Enter keyword to do a search (or just click Search to see everything),

3. Select the add-on you want and click Install.

That is it! Hopefully this makes your scripting experience even more exciting. :)

Bulk-change vCenter custom attributes

In this quick video, Aaron Newsome shows how he uses PowerGUI (and underlying PowerCLI) to quickly change custom attributes (such as Owner) across thousands of virtual machines. No scripting involved – just a few clicks in the UI. Great demo:

(Video “borrowed” from Mattias’s post on how his team is using this PowerGUI’s capability to set up vCenter monitoring with vFoglight.)

Advanced PowerShell Options in PowerGUI Script Editor

This add-on from James Brundage (from www.start-automating.com) lets you easily fine-tune the PowerShell host right in the PowerGUI Script Editor.

1. Download the PowerShell Preferences add-on from here,

2. Unblock the zip file,

3. Extract it to the My Documents \WindowsPowerShell \Modules folder,

4. In Script Editor’s File / PowerShell Libraries dialog box, select PowerShellPreferences.

And you will get this panel in the script editor, allowing you to change all the internal settings of the PowerShell host:

  • Command history size,
  • Error history size,
  • Mail server for send-mailmessage,
  • Strict mode (automated checking for variable initialization, etc.),
  • What-if mode (automatically running all cmdlets with -whatif flag),
  • Error level,
  • Warning level,
  • Debug level,
  • Verbose message level,
  • Progress message handling.

Combined, these give you incredible control over the way that PowerShell works – which in turn can help a lot when debugging your PowerShell scripts.

Download the add-on here.

Happy scripting!

Dmitry

Dynamsoft online source control in PowerGUI Script Editor

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:

  • Is a cloud system – so someone hosts that for you and can get to your files from anywhere,
  • It is free for up to 25 MB – and 25 MB is a lot of PowerShell scripts!

Learn more about Dynamsoft and get the step-by-step tutorial here.

Also, I have previously published similar tutorials on:

Unblocking PowerGUI Add-Ons and PowerShell Modules

When trying to use a Script Editor add-on or a PowerShell module or script you downloaded from the internet, you might every now and then get an error message like this:

Import-Module : File C:\Users\dsotnikov\Documents\WindowsPowerShell\Modules\Add-on.HelpBrowser\Add-on.HelpBrowser.psm1 cannot be loaded. The file C:\Users\dsotnikov\Documents\WindowsPowerShell\Modules\Add-on.HelpBrowser\Add-on.HelpBrowser.psm1 is not digitally signed. The script will not execute on the system. Please see “get-help about_signing” for more details..At line:1 char:184+ @(‘C:\Users\dsotnikov\Documents\WindowsPowerShell\Modules\Add-on.HelpBrowser\Add-on.HelpBrowser.psd1′) | Where-Object { @(Get-Module | %{$_.Path} ) -notcontains $_ } | %{ Import-Module <<<<  $_ }    + CategoryInfo          : NotSpecified: (:) [Import-Module], PSSecurityExc    eption    + FullyQualifiedErrorId : RuntimeException,Microsoft.PowerShell.Commands.ImportModuleCommand

This happens when the downloaded file comes from the internet, is not signed and thus conflicts with your PowerShell execution policy (e.g. RemoteSigned).

If you do trust this particular add-on/module/script to not be malicious (comes from a trusted source, has been inspected and so on), the workaround is quite easy – simply right-click the file (or the entire zip file if the files were zipped) and click Unblock in the Properties dialog box:

(You can also unblock files from PowerShell command-line – and in bulk! – by using Remove-DownloadFlag from PoshCode module.)

Hope this helps!

Dmitry

PowerShell Highlights of 2010

What were your key events of last year? Here’s my list:

PowerGUI Highlights

  • Reached 1,000,000 downloads (frankly, I still cannot fully comprehend that),
  • Released MobileShell - PowerShell server which gives you PowerShell command line (and scripts) to manage your IT in any computer browser or even mobile device: iPad, iPhone, Android, Blackberry, Windows Phone…
  • Script Editor is now extensible and has a rich set of add-ons adding almost any feature you could think of.

PowerShell for developers

PowerShell Projects

PowerShell Training

Contests

Usergroups

New cmdlets

A lot of companies and Microsoft product teams released cmdlets, modules, PowerPacks, etc.:

Books

Oh, and NASA started to use PowerShell to control their space craft. Almost. OK, not really… This was an April 1 joke. But wouldn’t it be cool if they did?

I know that the list seems a bit biased including a lot of PowerShell projects in which I was involved one way or another. This is not by intent and is a simple consequence of how memory works. :) This has been an amazing PowerShell year! Please add your PowerShell events of the year in the comments below!

Merry Christmas, Happy Holidays and a great New Year to all of you!

Enter-PSSession now working in PowerGUI

With 2.3 release we have finally implemented interactive remoting – so now you can use Enter-PSSession and Exit-PSSession right in the PowerGUI Script Editor. This is very handy in the PowerShell Console pane, when you want to quickly interactively connect to a remote server.

Enter-PSSession - interactive PowerShell remoting in PowerGUI Script Editor

We have long had support for other forms of remoting (New-PSSession, Invoke-Command, and so on) – now we finally are closing the loop with the addition of interactive remoting.

Learn more about what’s new in PowerGUI 2.3 and download it here!


My Recent Tweets

Legal

The posts on this blog are provided “as is” with no warranties and confer no rights. The opinions expressed on this site are mine and mine alone, and do not necessarily represent those of my employer - WSO2 or anyone else for that matter. All trademarks acknowledged.

© 2007-2014 Dmitry Sotnikov

April 2014
M T W T F S S
« Mar    
 123456
78910111213
14151617181920
21222324252627
282930  

Follow

Get every new post delivered to your Inbox.

Join 93 other followers

%d bloggers like this: