Posts Tagged ‘v2’


Which versions of PowerShell do you run?

Tuesday, March 8th, 2016 by June Blender
The PowerShell team released Windows PowerShell 5.0 on Windows 10 last year and just re-released Windows Management Framework (WMF) 5.0 for earlier versions of Windows. But, we know from years of experience that many people don't upgrade their versions quickly. It takes time to get to know and trust a new version. In a large enterprise, it takes time to do the parallel testing to certify that a new product is secure and compatible with the software that the organization uses. Take the survey: Which version of Windows PowerShell do you use? For those of us who are writing scripts and modules to share, this…   More »

PowerShell Scoping – Revisited

Wednesday, April 10th, 2013 by David Corrales
Yes, we said we would not speak of it again, but a user post provided a good example of the change in scoping rules between PowerShell V2 and V3. This particular user had a question about GUI controls on our new PowerShell GUIs forum and provided an example GUI script. In the example, the user declared a function inside an event script block: $OnLoadFormEvent={ #TODO: Initialize Form Controls here $t = dir c:\PowerShell\ $t2 = dir c:\Scoping\ function outTextBox1($textOut) { $richtextbox1.Text = $richtextbox1.Text + $textOut } } This script block is called when the GUI Window is about to display.…   More »

Out-GridView fails in PowerShell V2 after V3 update

Friday, December 21st, 2012 by David Corrales
Seems there was a recent update to PowerShell V3 that has affected PowerShell V2. Now the Out-Gridview  cmdlet produces an error and no longer functions in PowerShell V2. This issue affects all products using PowerShell including packaged scripts running in V2 mode. V2 only machines may not be affected To reproduce the error start PowerShell in v2 mode: powershell.exe –version 2.0   Next run the Out-GridView and you will get the following error:   We reported the issue to Microsoft using Connect:   [UPDATE] It seems this is by design, which in turn doesn’t make v3 fully backwards compatible.…   More »

PowerShell V3 support

Monday, October 22nd, 2012 by Alex Riedel
Just in case you missed it. With the latest service builds of PrimalScript 2012 and PowerShell Studio 2012 we added support for PowerShell V3. PrimalScript 2012 version switch   PowerShell Studio 2012 version switch   As you can see it’s pretty easy to switch which version you want to develop for, just press a button. Note that you must have V3 installed locally or a remote machine with an imported V3 cache for the corresponding button to be active. Also, on a Server 2012 or Windows 8 machine with the PowerShell V2 engine disabled, the V2 button may be grayed…   More »

PowerShell V2 Bug Introduced After Installing V3

Tuesday, September 25th, 2012 by David Corrales
As some of you may know, we are working on updating our products to support PowerShell V3 and have been running various tests to ensure our software functions correctly. During this testing process we stumbled upon a minor bug that was introduced into V2 after installing PowerShell V3 on Windows 7. As it turned out, this bug is also present on Windows 8 machines. Our goal is to inform you about this issue, should ever encounter it while using our PowerShell products. The following is a syntax error produced by a script using the V3 console. As you can see,…   More »

Why should you care about the PowerShell v2 CTP?

Saturday, May 10th, 2008 by Don Jones
Are there any features of Windows Vista you don't like (UAC comes to mind, for me)? What about Exchange? SQL Server? Windows Server? I'm sure you can come up with at least a few things that you just feel were *designed* wrong for the way you need them to work. Here's the problem with Microsoft users: Too many of us wait until Release Candidate (RC) phase to start playing with a product. After all, why should we debug Microsoft's code - which is really all the "beta" phase is about, right? Wrong. Take a look at the PowerShell v2 Community…   More »

A New PowerShell v2 CTP?

Thursday, April 24th, 2008 by Don Jones
Jeffrey Snover has been posting blog entries that are leading up to a new CTP of Windows PowerShell v2. Keep in mind that we'll be updating Windows PowerShell v2.0: TFM at the same time! So if you've bought it in the past, watch for an announcement, here in this blog, when a new revision is available.  Why buy a book about a product that isn't out, yet? First, it's a great way to get deep into the CTP quickly, and start testing new features. THIS is the time when the PowerShell team can make use of your feedback on HOW…   More »