Hi,
I wrote a simple mock application that'll make some automated calls to
com objects.


using System.Management.Automation;

namespace PWSApp
{
public partial class Form1 : Form
{
public Form1()
{
InitializeComponent();
}



private void Form1_Load(object sender, EventArgs e)
{
RunspaceInvoke rsi = new RunspaceInvoke();
rsi.Invoke("$WMP = new-object -ComObject WMPlayer.OCX");
rsi.Invoke("$WMP.openPlayer(\"SongName.mp3\");");

}
}
}

My Question here is,

What all should I ship with this executable (apart from .NET Framework
2.0) so that I can ensure that this application works on all machines.
Is there any specific dll that should be distributed so that PowerShell
specific features will work? Or is this bundled with .NET Framework
2.0?

Regards,
Mugunth

"Mugunth" wrote:

> What all should I ship with this executable (apart from .NET Framework
> 2.0) so that I can ensure that this application works on all machines.
> Is there any specific dll that should be distributed so that PowerShell
> specific features will work? Or is this bundled with .NET Framework
> 2.0?

AFAIK PoSh will be released as an optional Windows Update later this year.
Once all your machines have been updated and .NET Framework 2.0 is installed,
everything should be fine.

Copying only the core PoSh assemblies (System.Management.Automation etc.)
might work (I did not test it), but I doubt that this is recommended or
supported.

--
greetings
dreeschkind

> What all should I ship with this executable (apart from .NET Framework
> 2.0) so that I can ensure that this application works on all machines.
> Is there any specific dll that should be distributed so that PowerShell
> specific features will work? Or is this bundled with .NET Framework
> 2.0?

Let the PowerShell WU (windows update) install the necessary DLLs to the
GAC. Consider using the System.Activator class to late-bind to the
PowerShell types, and provide a nice error message to the user if PowerShell
isn't installed.

Andrew