Channel 9 - Entries tagged with POW2 Microsoft http://mschnlnine.vo.llnwd.net/d1/Dev/App_Themes/C9/images/feedimage.png Channel 9 - Entries tagged with POW2 http://channel9.msdn.com/Tags/pow2 Channel 9 keeps you up to date with the latest news and behind the scenes info from Microsoft that developers love to keep up with. From LINQ to SilverLight – Watch videos and hear about all the cool technologies coming and the people behind them. http://channel9.msdn.com/Tags/pow2 en Fri, 24 May 2013 00:43:34 GMT Fri, 24 May 2013 00:43:34 GMT Rev9 5 1 25 Windows PowerShell V2 IIS Provider
See additional information via MSDN Code Gallery.
]]> http://channel9.msdn.com/Blogs/philpenn/How-to-use-the-New-PowerShell-V2-IIS-Provider This video demonstration provides and introduction to the new Windows PowerShell provider for IIS available new with Windows Server 2008 R2. See additional information via MSDN Code Gallery. http://channel9.msdn.com/Blogs/philpenn/How-to-use-the-New-PowerShell-V2-IIS-Provider Tue, 05 May 2009 20:16:00 GMT http://channel9.msdn.com/Blogs/philpenn/How-to-use-the-New-PowerShell-V2-IIS-Provider Phil Pennington Phil Pennington 0 http://channel9.msdn.com/Blogs/philpenn/How-to-use-the-New-PowerShell-V2-IIS-Provider/RSS POW2 PowerShell PSV2 R2 R2IIS w2k8r2 Windows Server 2008 R2 Windows PowerShell V2 Remote Sessions
See more info about Windows PowerShell V2 at MSDN Code Gallery.

]]> http://channel9.msdn.com/Blogs/philpenn/PowerShell-V2-Remote-Sessions This video demonstrates using Windows PowerShell V2 remote sessions.   This is a new feature with V2 and available natively within Windows 7 and Windows Server 2008 R2. See more info about Windows PowerShell V2 at MSDN Code Gallery. 510 http://channel9.msdn.com/Blogs/philpenn/PowerShell-V2-Remote-Sessions Sat, 02 May 2009 23:32:00 GMT http://channel9.msdn.com/Blogs/philpenn/PowerShell-V2-Remote-Sessions Phil Pennington Phil Pennington 0 http://channel9.msdn.com/Blogs/philpenn/PowerShell-V2-Remote-Sessions/RSS POW2 PowerShell PSV2 R2efficient w2k8r2 Windows Server 2008 R2 Windows PowerShell V2 Modules This video demonstrates converting a Windows PowerShell script to a Windows PowerShell module.

See more info at MSDN Code Gallery.

The video starts by introducing a simple script file, counter.ps1, with three functions and two variables.

The script file is dot sourced into the environment.  All variables and functions are now in scope.  The intent is to only have two of the functions in scope, with the rest being private implementation details.

Next, the file is renamed from counter.ps1 to counter.psm1 for the correct module extension.  Using the Import-Module cmdlet, the module is loaded into scope.  It is demonstrated that the variables are private, however all functions are public.  This is shown using Get-Command -module counter to list the exported commands.

Before changing the module it is necessary to remove it from scope.  This is accomplished using Get-Module | Remove-Module to pipe any modules (only one in this sample) to be removed.

In order to hide certain functions, it is necessary to specific which are public using Export-ModuleMember function_name.  By specifying only the intended public functions, others remain private, only accessible from within the module.

 

]]> http://channel9.msdn.com/Blogs/philpenn/PowerShell-V2-Modules This video demonstrates converting a Windows PowerShell script to a Windows PowerShell module. See more info at MSDN Code Gallery. The video starts by introducing a simple script file, counter.ps1, with three functions and two variables. The script file is dot sourced into the environment.  All variables and functions are now in scope.  The intent is to only have two of the functions in scope, with the rest being private implementation details. Next, the file is renamed from counter.ps1 to counter.psm1 for the correct module extension.  Using the Import-Module cmdlet, the module is loaded into scope.  It is demonstrated that the variables are private, however all functions are public.  This is shown using Get-Command -module counter to list the exported commands. Before changing the module it is necessary to remove it from scope.  This is accomplished using Get-Module | Remove-Module to pipe any modules (only one in this sample) to be removed. In order to hide certain functions, it is necessary to specific which are public using Export-ModuleMember function_name.  By specifying only the intended public functions, others remain private, only accessible from within the module.   346 http://channel9.msdn.com/Blogs/philpenn/PowerShell-V2-Modules Thu, 09 Apr 2009 19:41:00 GMT http://channel9.msdn.com/Blogs/philpenn/PowerShell-V2-Modules Phil Pennington Phil Pennington 1 http://channel9.msdn.com/Blogs/philpenn/PowerShell-V2-Modules/RSS POW2 PowerShell PSV2 w2k8r2 Windows 7 Windows Server 2008 R2 Windows PowerShell V2 Sessions and Debugging This video demonstration walks through the steps of creating and using sessions in Windows PowerShell v2.  It also introduces the debugging functions such as working with breakpoints.

See additional information via MSDN Code Gallery.

Demo:

The Universal Code Execution Model means that you can run your cmdlets, scripts, and functions in any session, locally or remotely.  A Windows PowerShell session is actually a persistent connection to the computer using the Windows Remote Management (WinRM) service.  Creating sessions is performed using the New-PSSession cmdlet. 

First, display the current process ID using the $pid environment variable.  Next, create a new session on the localhost using New-PSSession.

The Invoke-Command cmdlet will cause script to be invoked on the given session, and in this case will simply output the value of $pid, the process ID, on the given session.  This is a quick way to verify that the session is truly a different process from the original state.

The Get-PSSession cmdlet will display any running sessions.  This does not include your terminal window which is not managed as a connection.  Without running New-PSSession, the Get-PSSession cmdlet will not return any objects.

Next, execute the Some-Functions.ps1 script file containing a simple Square-Root function.  Once invoked, you can execute the functions in the session, but not in the local terminal.  The Import-PSSession cmdlet, run next, imports the sqrtAdvance function so it can be used locally.

Finally, the Remove-PSSession cmdlet is invoked to destroy the session and its underlying connection.  Calling Get-PSSession confirms that it is no longer active.

Next, the video covers debugging using the Integrated Scripting Environment (ISE).  The Set-PSBreakpoint cmdlet allows you to declare a breakpoint on a line, variable, or command.  In the video, the breakpoint is placed on the variable "s1" which is the session variable.  A breakpoint also specifies AccessMode, by default, Write.  As soon as anything attempts to modify the value of "s1" code execution will break.

The existing script for working with sessions is started and as soon as the New-PSSession cmdlet is run, the breakpoint takes effect.  ISE has a Debug menu which supports creating and managing breakpoints, stepping through and resuming code, and evening showing the call stack.  The video steps through the code and demonstrates these features.

]]> http://channel9.msdn.com/Blogs/philpenn/PowerShell-V2-Sessions-and-Debugging This video demonstration walks through the steps of creating and using sessions in Windows PowerShell v2.  It also introduces the debugging functions such as working with breakpoints. See additional information via MSDN Code Gallery. Demo: The Universal Code Execution Model means that you can run your cmdlets, scripts, and functions in any session, locally or remotely.  A Windows PowerShell session is actually a persistent connection to the computer using the Windows Remote Management (WinRM) service.  Creating sessions is performed using the New-PSSession cmdlet.  First, display the current process ID using the $pid environment variable.  Next, create a new session on the localhost using New-PSSession. The Invoke-Command cmdlet will cause script to be invoked on the given session, and in this case will simply output the value of $pid, the process ID, on the given session.  This is a quick way to verify that the session is truly a different process from the original state. The Get-PSSession cmdlet will display any running sessions.  This does not include your terminal window which is not managed as a connection.  Without running New-PSSession, the Get-PSSession cmdlet will not return any objects. Next, execute the Some-Functions.ps1 script file containing a simple Square-Root function.  Once invoked, you can execute the functions in the session, but not in the local terminal.  The Import-PSSession cmdlet, run next, imports the sqrtAdvance function so it can be used locally. Finally, the Remove-PSSession cmdlet is invoked to destroy the session and its underlying connection.  Calling Get-PSSession confirms that it is no longer active. Next, the video covers debugging using the Integrated Scripting Environment (ISE).  The Set-PSBreakpoint cmdlet allows you to declare a breakpoint on a line, variable, or command.  In the video, the breakpoint is placed on the variable " 809 http://channel9.msdn.com/Blogs/philpenn/PowerShell-V2-Sessions-and-Debugging Thu, 09 Apr 2009 19:17:00 GMT http://channel9.msdn.com/Blogs/philpenn/PowerShell-V2-Sessions-and-Debugging Phil Pennington Phil Pennington 2 http://channel9.msdn.com/Blogs/philpenn/PowerShell-V2-Sessions-and-Debugging/RSS POW2 PowerShell PSV2 w2k8r2 Windows 7 Windows Server 2008 R2 Windows PowerShell V2 Functions Creating functions in Windows PowerShell is an easy way to extend the environment without resorting to code compilation and complicated deployment steps.

By using functions along with the right attributes and parameters, you can create first-class code extensions in PowerShell v2 without ever opening Visual Studio. 

See additional details on this and other Windows PowerShell V2 features at MSDN Code Gallery.

]]> http://channel9.msdn.com/Blogs/philpenn/PowerShell-V2-Functions Creating functions in Windows PowerShell is an easy way to extend the environment without resorting to code compilation and complicated deployment steps. By using functions along with the right attributes and parameters, you can create first-class code extensions in PowerShell v2 without ever opening Visual Studio.  See additional details on this and other Windows PowerShell V2 features at MSDN Code Gallery. 384 http://channel9.msdn.com/Blogs/philpenn/PowerShell-V2-Functions Thu, 09 Apr 2009 19:01:00 GMT http://channel9.msdn.com/Blogs/philpenn/PowerShell-V2-Functions Phil Pennington Phil Pennington 0 http://channel9.msdn.com/Blogs/philpenn/PowerShell-V2-Functions/RSS POW2 PowerShell PSV2 w2k8r2 Windows 7 Windows Server 2008 R2