so .Net 4 added named and optional parameters which are pretty sweet. I don’t need to make as many 1 line overload methods.
Will that work over WCF?
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
so .Net 4 added named and optional parameters which are pretty sweet. I don’t need to make as many 1 line overload methods.
Will that work over WCF?
Since these are compiler semantics I’d say no. However you’d expect them to work in the only following way.
On the Service Code side all code would accept the defaulted parameters.
On the client side I note that the ‘Add Service Reference’ tooling on VS2010 doesn’t take the defaults and add them to the generated proxy. So You’d have to generate you’re own proxy.
In this way the client code can use the defaults if the the default is specified in the client side contract implementation.
I would be that the same is true for the named parameters.
All in all yes, but the stuff is not carried over WCF. All that happens is that the client proxy will have to send into the channel factory as a proper parameter.