faultcontract

Take for example a project with 10 services and 20 methods on each service. All services inherit from a base services which has a security check. The first thing each method does is to make a call to the security check. This throws a security exception if there is a problem. Question is: Do I need to specify a FaultContract on each method (OperationContract), or can I do it once in a central definition? No, you need to do it on each and every method - WCF is rather picky and requires explicit settings pretty much for everything (which really is a good thing in the end, I am convinced). Marc

I have put the attribute [FaultContract(typeof(ExceptionDetail))] for my operation contract. When I am trying to add the service to a client application, I get this error - "Custom tool error: Failed to generate code for the service reference 'ServiceReference1'. Please check other error and warning messages for details." But when I comment out the FaultContract Attribute, I am able to add the wcf service reference th' my client app. The point of having FaultContracts is to make it possible to first of all pass back SOAP faults from the service which will not break the communication channel

I've read all there is to read on this, but maybe I'm missing something (well, definitely I'm missing something otherwise it would be working already) I'm throwing some exception error inside my server business layer: public class RfcException : Exception { public RfcException(string _m, Exception _inner) : base(_m, _inner) { } public Dictionary<string, string> ExtendedProperties { get { return extendedProperties; } protected set { extendedProperties = value; } } private Dictionary<string, string> extendedProperties = new Dictionary<string, string>(); } which I leave unhandled in the service,