title: Configuration for PowerShell module created via .NET framework
body: <p>What's the best practice when you have dependencies that you want to be able to configure when creating a PowerShell module in C#?</p>
  
  <p>My specific scenario is that the PowerShell module I am creating via C# code will use a WCF service.  Hence, the service's URL must be something that the clients can configure.  </p>
  
  <p>Is there a standard approach on this?  Or will this be something that must be custom implemented?</p>