Wcf – System.ServiceModel.ServiceHost, cannot be used for communication because it is in the Faulted state

Actually, although I blogged (see Luke's answer), I think this is better than my IDisposable wrapper. Typical code:

Service<IOrderService>.Use(orderService=>
{
  orderService.PlaceOrder(request);
}); 

(edit per comments)

Since Use returns void, the easiest way to handle return values is via a captured variable:

int newOrderId = 0; // need a value for definite assignment
Service<IOrderService>.Use(orderService=>
  {
    newOrderId = orderService.PlaceOrder(request);
  });
Console.WriteLine(newOrderId); // should be updated

When you ask a question about an exception, you should post the entire exception, including all InnerException instances. You should catch the exception, display ex.ToString(), then rethrow the exception with "throw":

try {
    // Do whatever causes the exception
} catch (Exception ex) {
    Console.WriteLine(ex.ToString());  // Or Debug.Print, or whatever
    throw; // So exception propagation will continue
}

In this case, I wonder if you have a using block around your proxy instantiation:

using (var proxy = new WcfProxyClient())
{
    // Use of proxy
}

There is a design flaw in WCF that makes this about the only place in .NET where you should not use a using block. Instead, you need to do it by hand. See http://web.archive.org/web/20100703123454/http://old.iserviceoriented.com/blog/post/Indisposable+-+WCF+Gotcha+1.aspx.

Also, see "What is the best workaround for the WCF client using block issue?" and "Indisposable WCF clients".