Linking against RC2

PowerShell Team

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:


PS>[appdomain]::currentdomain.getassemblies() |

where {($_.fullname -match “”) -OR ($_.fullname –match “Microsoft”)} |

copy-item -path {$_.location} -destination c:\sdk\ -verbose



Jeffrey Snover [MSFT]
Windows PowerShell/MMC Architect
Visit the Windows PowerShell Team blog at:
Visit the Windows PowerShell ScriptCenter at:


NOTE: Added January 5th, 2009 – If you add a hard coded reference to C:\Sdk in your visual studio projects,  then two side effects will happen.  First, your project will not work if the sdk is not in C:\SDK.  Second, you will only have as up-to-date assemblies as are in C:\SDK.  I personally edit the .csproj files with notepad, find an existing reference (e.g. System.Xml), copy and paste this item, and change the reference to System.Management.Automation.  This builds against the most up-to-date System.Management.Automation reference on the system.


Hope this Helps,

James Brundage [MSFT]  


Discussion is closed.

Feedback usabilla icon