Windows PowerShell Team Blog : PowerShell

Microsoft Script Explorer: Next Steps

Windows PowerShell Blog — Fri, 05 Apr 2013 19:56:00 GMT

For those who are familiar with Microsoft Script Explorer for Windows PowerShell, you know that we haven't released additional updates to it since we published the release candidate (RC) in August 2012. Over the past few months, we have been talking with customers and partners and taking a hard look at the adoption rate of the RC in terms of the number of downloads and the feedback we're received...(read more)

Windows PowerShell 3.0 SDK Sample Pack

Windows PowerShell Blog — Sun, 17 Mar 2013 22:45:00 GMT

We're pleased to announce the availability of the Windows PowerShell 3.0 SDK Sample Pack. For Windows PowerShell 3.0, the SDK samples work a little differently than in previous releases of Windows PowerShell. For Windows PowerShell 2.0, we released a separate standalone SDK to the Download Center at http://go.microsoft.com/fwlink/?LinkID=180421 . This download contained both the reference assemblies...(read more)

Updatable Help speaks only English! What’s up with that?

Windows PowerShell Blog — Thu, 17 Jan 2013 19:20:00 GMT

Our customers have certainly not been shy about their interest in multiple languages of Windows PowerShell Updatable Help, and we're grateful to hear how much they would value localized Help. Our challenge is this: Updatable Help is a new feature for this release of Windows PowerShell, and we have so very many new cmdlets and modules for Windows PowerShell 3.0 (over 2,300 new cmdlets in 95 modules...(read more)

New-Workflow –MakeItEasy: Authoring Workflows using PowerShell Extended Syntax

Windows PowerShell Blog — Sat, 21 Jul 2012 20:06:00 GMT

Some time back, in his blog post , Jeffrey Snover introduced one of the new Windows PowerShell 3.0 feature – Windows PowerShell Workflow . In that post, you saw a glimpse of how to author workflows using PowerShell syntax. This post dives into more details of authoring workflows using PowerShell syntax and various extensions to it. Why we chose to extend the PowerShell Language for Workflow Authoring...(read more)

High Level Architecture of Windows PowerShell Workflow (Part 1)

Windows PowerShell Blog — Fri, 15 Jun 2012 11:55:00 GMT

1 Summary In March we introduced Windows PowerShell Workflow (PSWF), which explained why we integrated workflows with PowerShell, and what were our major investment areas for our first release. In a recent post , Jeffrey Snover summarizes this decision: “ We integrated the Windows Workflow Foundation engine into PowerShell to make it simple and easy to automate things that take a long time,...(read more)

When Windows PowerShell Met Workflow

Windows PowerShell Blog — Sat, 17 Mar 2012 03:08:19 GMT

Meet the new kid on the block! Windows PowerShell Workflow (PSWF) is the latest addition to the Windows PowerShell family. First, let’s establish the context for the decision to integrate workflows into Windows PowerShell. It starts with cloud computing and Windows-based datacenters. Cloud computing provides a set of highly available, scalable computing services that leverage high volume components...(read more)

Peering into script modules

Windows PowerShell Blog — Wed, 03 Jun 2009 12:49:00 GMT

Sometimes it’s handy to access internal elements of script modules. For instance you may be using a 3rd party module in your application and would like to see the internal state for debugging purposes. This can be accomplished with the invoke operator (&) which allows you to access a modules session state: & $module {script block} The script block is executed in the context of the module. Create...(read more)

Differences between the ISE and PowerShell console

Windows PowerShell Blog — Fri, 17 Apr 2009 19:32:00 GMT

Here is a collection of differences between the PowerShell_ise.exe and PowerShell.exe, as well as workarounds and suggestion if you need them (assuming we have them :)) Limited support for interactive console apps, try cmd.exe, then try cmd.exe /k cmd.exe /c dir still works though, and more information is available here http://blogs.msdn.com/powershell/archive/2009/02/04/console-application-non-support...(read more)