WCF: Null Parameter on Service Call

Was receiving a null parameter on a service call. After looking through KnownTypes, Asynchronous vs synchronous, etc. more a while, turns out:

The parameter on the asynchronous OperationContract was named request, whereas the parameter on the synchronous OperationContract was named command.

Wow.

"If your WCF service is receiving null values instead of the parameters you are expecting, check that the parameter names on your methods on the client version of the contract match those on the server version of the contract. And on the client side, be sure to check both the synchronous and asynchronous definitions of your methods."

Thanks to the above quote from http://blog.functionalfun.net/2009/09/if-your-wcf-service-is-unexpectedly.html

Advertisement

« Gotcha: nHibernate NonUniqueObjectException