MSDN
Get flash to fully experience Pearltrees
Adding Custom Cmdlet Help for Providers - Windows PowerShell Blog
A new feature of Windows PowerShell 2.0 lets you write custom cmdlet help for Windows PowerShell providers. This blog explains how to do it. (The topic will also be covered in excruciating detail in MSDN, but we don't want you to wait.) What's a Provider? A Windows PowerShell provider is a C# program that exposes a data store to Windows PowerShell through a Windows PowerShell drive (PSDrive).
Twas the night before Christmas, and all through the net PowerShell lovers were wondering exactly what they might get Their readers were ready, their minds were aware That more joy of CTP3 would soon be there A cmdlet, a function? What has the PowerShell team done? How about a whole module, to share scripts with everyone?
Merry Christmas From PowerShell: The CodeDownloader Module - Windows PowerShell Blog
Get-CommandPlugin - Windows PowerShell Blog
One of the nifty new CTP3 features is command and parameter meta data on functions. In V1, you had to parse a function yourself to extract the parameters. In CTP2, you could use the tokenizer API to parse the function, but extracting parameters this was is error prone. In CTP3, and in V2, you can actually get a dictionary of parameters on the FunctionInfo object. Check it out: Get-Command -type Function | Foreach-Object { $_.Parameters }
One source of input for a cmdlet is the command line. This section describes how to add a parameter to the Get-Proc cmdlet (described in Creating a Cmdlet without Parameters ) so that the cmdlet can process input from the local computer based on explicit objects passed to the cmdlet. The Get-Proc cmdlet described here retrieves processes based on their name, and then displays information about the processes at the command line. Topics in this section include the following: Defining the Cmdlet Class The first step in cmdlet creation is always cmdlet naming and the declaration of the .NET class that implements the cmdlet.
Adding Parameters that Process Command-Line Input
“Writing a Windows PowerShell Host application” is for developers who are designing or writing applications that host Windows PowerShell 2.0. The host application can, define the runspace where commands are run, open sessions on a local or remote computer, and invoke the commands either synchronously or asynchronously based on the needs of the application. This document focuses on how to write host applications that use the PowerShell class (introduced in Windows PowerShell 2.0) to invoke commands programmatically. This class provides a simpler solution for creating host applications then those APIs available in Windows PowerShell 1.0. In This Section See Also
Writing a Windows PowerShell Host Application
Using PowerShell to read xml-files - Little more than out of the box development
A couple of months ago a colleague and I decided to try to build a demo-environment for SharePoint. We wanted to be able to take a new fresh installed Windows 2003 (or 2008) server, and just run a PowerShell script and then the environment should be up and running. The environment should of course include sample data, sites, and last but not least a number of users. In order to do this we first had to learn PowerShell. Always fun to learn new things! This post is about how we use PowerShell to read the userdata from the xml-file.
Cmdlets can perform their action internally or as a Windows PowerShell background job. When a cmdlet runs as a background job, the work is done asynchronously in its own thread separate from the pipeline thread that the cmdlet is using. From the user perspective, when a cmdlet runs as a background job, the command prompt returns immediately even if the job takes an extended amount of time to complete, and the user can continue without interruption while the job runs. Jobs, Child Jobs, and the Job Repository
Background Jobs
Designing useable cmdlets is part engineering and part art. It’s not an easy task to define the conceptual boundaries of a cmdlet (where does one cmdlet end and the next begin) or to provide great feature control without inundating the user with parameters. However, you can improve the usability of your cmdlets by avoiding two common parameter set design flaws. A parameter set with no mandatory parameters in a cmdlet that requires parameters Mandatory parameters with position numbers that are higher than the position numbers of optional parameters Parameter sets with no mandatory parameters
Improving Parameter Set Design - Windows PowerShell Blog
Designing Cmdlets That Have Lots of Parameters - Windows PowerShell Blog
We often get the question of what to do about a cmdlet that has lots of parameters. Do you break it up into multiple commands or just have a single cmdlet with lots of parameters. Here is the way I think about it: If you have to enter 100 things to get a job done, it doesn’t really matter whether you enter those 100 things via 1 cmdlet with 100 parameters or 10 cmdlets with 10 parameters each.
Description PowerBook is the Facebook Module for Windows PowerShell. PowerBook allows you to use many of Facebook features and interact with Facebook via Windows PowerShell. PowerBook contain 24 PowerShell functions that allow you to do most of Facebook actions. PowerBook is the result of integration between Windows PowerShell and Facebook Developer’s Toolkit v3.0. The story behind PowerShell PowerBook
PowerShell PowerBook