I'm spoiled by PowerShell's New-WebServiceProxy. I want to poke around at a WCF but I don't want to precompile a WSDL, or add a service reference, or include a contract interface that'll break on compile when it changes. Let me just interact with the web services reflectively like I do in PowerShell. The performance profile is terrible. It does …

DynamicWebServiceProxy.cs

using System;
using System.Linq;
using System.Management.Automation;
using System.Management.Automation.Runspaces;
using System.Reflection;

namespace Xcud.Net
{
    /// <example>
    /// DynamicWebServiceProxy proxy = new DynamicWebServiceProxy(uri);
    /// string[] cachePaths = proxy.InvokeMethod("GetCachePaths", null) as string[];
    /// </example>
    public class DynamicWebServiceProxy
    {
        object Proxy = null;
        public DynamicWebServiceProxy(string uri)
        {
            Pipeline pipeline = PowerShell.Create().Runspace.CreatePipeline();
            Command command = new Command("New-WebServiceProxy");
            command.Parameters.Add(new CommandParameter("Uri", uri));
            pipeline.Commands.Add(command);

            PSObject proxyResult = pipeline.Invoke().FirstOrDefault();

            this.Proxy = proxyResult.BaseObject;
        }

        public object InvokeMethod(string methodName, object[] parameters)
        {
            MethodInfo method = this.Proxy.GetType().GetMethod(methodName);
            if (method == null)
                return null;

            return method.Invoke(this.Proxy, parameters);
        }
    }
}

See what I did there? I got in the first heckle.