Browse by Tags
All Tags »
WCF »
.NET (
RSS)
A short discussion ensued today on the topic of Code Generation tools like CodeSmith. Like Unit Testing, code generation is a topic that some people swear by and some reject out of hand. I'm sure this is mostly a question of getting used to the concept...
This is the last part of my continuing saga of serializing dictionaries over WCF and beyond. Quick recap: While WCF allows me to serialize an IDictionary easily, trying to serialize that dictionary later for other uses fails - specifically, caching it...
One of WCF's goals is interoperability with standard protocol stacks, like WSE or other WS-* implementations. This led, I am told, to the design of WCF's default object serializer - the DataContractFormatSerializer. This handy little engine serializes...
I've been using WCF for the past few months and on the whole, I think the programming model works. I'm getting to really like the extensibility model and the whole deal seems to click rather well. One place where I feel it's a bit broken,...
WCF's Instance Context model allows me to specify my service's instantiation behavior - I can get a new instance for every call, have WCF manage a session for me and keep an instance per session, or just get lazy and have my service instantiated as a...
As I mentioned in my previous post, I have a need to consistently pass an operation context to any thread I choose to spin. Doing so manually, as I did here, involves a lot of ugly, repetitive code for every thread. A lot of room for mistakes and bugs...
WCF Services tend to be big, heavy duty things. When I write a service I often want it to do a lot of work for a lot of clients, and it should do it efficiently. This usually means that I will use multithreaded code to get things done concurrently. Whether...
When using WCF services, we have several options for creating the proxies. We can create them statically using SVCUTIL or the build-in IDE support (Add Service Reference...), or we can generate them dynamically using the ChannelFactory<T> or GenericProxy<T>...
Another error message that stumped me today (after I had removed the IsOneWay parameter and actually got to see it) was the following exception: System.ServiceModel.CommunicationException The server did not provide a meaningful reply; this might be caused...
The first step in understanding WCF error messages is making sure you actually get them. You can have an OperationContract defined with the IsOneWay parameter set to True, thus optimizing it by not requiring a reply message. Since faults and exceptions...
More Posts
Next page »