webinvoke

I have written a REST Service in WCF in which I have created a method(PUT) to update a user. for this method I need to pass multiple body parameters [WebInvoke(Method = "PUT", UriTemplate = "users/user",BodyStyle=WebMessageBodyStyle.WrappedRequest)] [OperationContract] public bool UpdateUserAccount(User user,int friendUserID) { //do something return restult; } Although I can pass an XML entity of user class if there is only one parameter. as following: var myRequest = (HttpWebRequest)WebRequest.Create(serviceUrl); myRequest.Method = "PUT"; myRequest.ContentType = "application/xml"; byte[] data

I am currently developing a Windows Service hosted WCF service. One of the methods has a URI which is set up to receive a callback from a payment provider. This is the interface contract... [OperationContract] [WebInvoke(UriTemplate = "3DSecureCallback?TrxId={id}", Method = "POST", BodyStyle = WebMessageBodyStyle.Bare)] void ThreeDSecureCallBack(string id, Stream body); This issue I am having is that the 3rd party provider posts to our service. I have to provide a callback url to it. So we can reconcile payments, we provide a URL with a query string parameter containing the transaction id.

This question already asks what I'm asking, but I want some clarification on the answer. The answer states that WebGet and WebInvoke are similar, and that the primary difference is the Method parameter. But if the Method parameter is set to "GET" , is it actually functionally equivalent, or are there other differences? They are simply marker attributes and end up being 100% functionally equivalent. The only thing that interprets these attributes is the WebHttpBehavior::GetWebMethod method and its functionality is simply: internal static string GetWebMethod(OperationDescription od) {