WCF

WCF – Be ware of the field ordering when using DataContractSerializer

One of the less known aspect of the DataContractSerializer is its dependency on the order in which fields are serialized and deserialized. As this article points out, the basic rules for ordering include: If a data contract type is a part of an inheritance hierarchy, data members of its base types are always first in …

WCF – Be ware of the field ordering when using DataContractSerializer Read More »

WCF – Data Contract version round-tripping using IExtensibleDataObject

With WCF, provided that you’re using the DataContractSerializer and not the NetDataContractSerializer, you have a certain degree of protection against data contract changes from the client’s perspective. Existing contracts will still work if existing members are not removed from the data contract, which means you are free to add new members to the data contract …

WCF – Data Contract version round-tripping using IExtensibleDataObject Read More »

WCF – Using the NetDataContractSerializer to share your type

DataContractSerializer For those of your who are familiar with WCF you would no doubt know about the DataContractSerializer class, the DataContractSerializer does not include the CLR type information in the serialized XML, which allows for loose coupling between the client and server because they don’t have to share the same CLR types. However, this also …

WCF – Using the NetDataContractSerializer to share your type Read More »

.Net Tips – Using custom ServiceThrottlingAttribute to specify WCF service throttling behaviour

If you have created a WCF service in the past then I assume you’re aware that WCF is very heavily configuration-driven and that you can specify the service behaviour including the throttling parameters (MaxConcurrentCalls, MaxConcurrentInstances, MaxConcurrentSessions) in the config file. But to specify the type of service (PerCall, PerSession or Singleton) you need to apply …

.Net Tips – Using custom ServiceThrottlingAttribute to specify WCF service throttling behaviour Read More »

.Net Tips – using configSource or file attribute to externalize config sections

There’s a little known attribute which was introduced in the .Net framework 2.0 called configSource, which allows you to externalize sections of the configuration file. It works just like the optional file attribute found on the appSettings element: <appSettings file = “relative file name” /> but can be added to any configuration section to specify …

.Net Tips – using configSource or file attribute to externalize config sections Read More »

By continuing to use the site, you agree to the use of cookies. more information

The cookie settings on this website are set to "allow cookies" to give you the best browsing experience possible. If you continue to use this website without changing your cookie settings or you click "Accept" below then you are consenting to this.

Close