The reason people recommend to avoid enums in webservices is because they create subtle backwards compatible problems. The same applies to regular enums but in web services the problem is even more clear specially in .NET-generated proxies (see below). If the enumerate is input only you have no issues. If the enumerate can be an … Read more
Client side: SendTimeout is used to initialize the OperationTimeout, which governs the whole interaction for sending a message (including receiving a reply message in a request-reply case). This timeout also applies when sending reply messages from a CallbackContract method. OpenTimeout and CloseTimeout are used when opening and closing channels (when no explicit timeout value is … Read more
Security. You’re not granting DB access to anyone but web server/app user. This is extra important when you have tons of users. You avoid the pain of user/role maintenance on DB side. DB load reduction. Web service can cache the data it retrieved from DB. Database connection pooling (hat/tip @Dogs). A web service can use … Read more
Fields are in the wrong order for your message. DataContracts default to Alphabetical ordering and not order of declaration; and expects XML elements to arrive in that order; Out of order elements are discarded usually. Either fix your contract to specify the right order explicitly (using the Order property of the DataMemberAttribute) or make sure … Read more
The way I do this is by projecting the data I want to serialize into an anonymous type and serializing that. This ensures that only the information I actually want in the JSON is serialized, and I don’t inadvertently serialize something further down the object graph. It looks like this: var records = from entity … Read more
This doesn’t help you in 3.0, but I can just see people finding this question and being frustrated because they are trying to get the client IP address in 3.5. So, here’s some code which should work: using System.ServiceModel; using System.ServiceModel.Channels; OperationContext context = OperationContext.Current; MessageProperties prop = context.IncomingMessageProperties; RemoteEndpointMessageProperty endpoint = prop[RemoteEndpointMessageProperty.Name] as RemoteEndpointMessageProperty; … Read more
A “ContractFilter mismatch at the EndpointDispatcher” means the receiver could not process the message because it did not match any of the contracts the receiver has configured for the endpoint which received the message. This can be because: You have different contracts between client and sender. You’re using a different binding between client and sender. … Read more
There’s a blog post which suggests implementing an IExtension<T>. You may also take a look at this discussion. Here’s a suggested implementation: public class WcfOperationContext : IExtension<OperationContext> { private readonly IDictionary<string, object> items; private WcfOperationContext() { items = new Dictionary<string, object>(); } public IDictionary<string, object> Items { get { return items; } } public static … Read more
Currently your web method return a String together with ResponseFormat = WebMessageFormat.Json. It follow to the JSON encoding of the string. Corresponds to www.json.org all double quotes in the string will be escaped using backslash. So you have currently double JSON encoding. The easiest way to return any kind of data is to change the … Read more
Since a lot of programmers were overwhelmed with the [DataContract] and [DataMember] attributes, with .NET 3.5 SP1, Microsoft made the data contract serializer handle all classes – even without any of those attributes – much like the old XML serializer. So as of .NET 3.5 SP1, you don’t have to add data contract or data … Read more