I don't know such namespace. Here is the thing: Power Shell is the interpretive system; and you need to loads some additional assembly which is not loaded by default. As everything in interpretive system, it needs to be loaded "during runtime", dynamically. How? I'll demonstrate how to load an assembly from GAC, if the (default) versions automatically matching the .NET versions your version of Power Shell is targeted to. For example, this is how you can load and use Forms:
$null = [System.Reflection.Assembly]::LoadWithPartialName("System.Windows.Forms")
All the code written after this line is executed can use
System.Windows.Forms.Forms
,
System.Windows.Forms.Application
and other declaration required to create windows UI working in PowerShell (I do have such application). Same thing about WPF or nearly any other .NET FCL libraries not loaded by default.
The same way you can load the extra assemblies you need for your functionality. If your assembly is not in GAC, you can load it in some other way. Look at all the methods named
[System.Reflection.Assembly]::Load
:
http://msdn.microsoft.com/en-us/library/System.Reflection.Assembly%28v=vs.110%29.aspx[
^].
This mechanism is pretty non-trivial and specific to Power Shell as interpretive system.
—SA