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.
A fairly common question cmdlet developers have is “How do I invoke a cmdlet from within a cmdlet”. This usually comes up when converting a script or function into a compiled cmdlet. Marco Shaw is writing a nice series of blog posts covering this topic using the PowerGadgets cmdlets as examples.
The RC2 SDK is not yet available. Until it is, here is a quick and dirty way for you to find/extract the DLLs to link your code against. Do this from a RC2 shell and you’ll a copy of the DLLS in C:\SDK:
A summary of the Namespaces PowerShell defines and uses.
System.Management.Automation serves as the root namespace for PowerShell. The namespace contains the types a developer would use to implement a Cmdlet.
Sub-namespaces are defined for specific sections of the API that are used by specific types of developers.