A while back I showed how to call a Web Service from PowerShell.  It was pretty easy.  Doing the same for a Windows Communication Foundation service is just about as easy.  The only wrinkle is in specifying the binding and the endpoint address.  WCF steers folks towards specifying this binding/endpoint address data in their application's configuration file.  However it just doesn't seem right to create a config file for PowerShell.exe.  Fortunately it is pretty easy to specify this information programmatically in PowerShell script.

 

The following is using the self-hosted WCF service app that you get when you install the latest Windows SDK.  After you have installed .NET FX 3.0 runtime and the Windows SDK, extract the WCFSamples.zip file in place.  The ZIP file is located in:
 
C:\Program Files\Microsoft SDKs\Windows\v6.0\Samples
 
Then open this solution:
 
C:\Program Files\Microsoft SDKs\Windows\v6.0\Samples\TechnologySamples\Basic\Service\Hosting\SelfHost\CS\SelfHost.sln
 
and set the Service project as the startup project and then run the service.
 
Now open up the PowerShell prompt.  Before doing anything else you will need to have the environment configured to compile using the C# 2.0 compiler.  See my blog post on how to configure the VS 2005 specific variables in PowerShell.  Another alternative (and probably better) is to use Lee Holme's script to execute the standard vsvars80.bat file in a way that sets those environment variables in the PowerShell variable space.
 
Once you have the VS 2005 variables configured, execute the following commands from the directories indicated.  Note: on 7# you may need to execute it twice if it fails the first time usually because of the Windows firewall.  I had to unblock it via Windows Live One Care and execute that command again to get it to work.
 

 
OK there it is.  Nothing too exciting in terms of the results but hey we have PowerShell working with .NET 3.0, specifically Windows Communication Foundation.  Pretty cool!