Transformation Header Contract For Free

this video we'll discuss message contracts in WCF this is continuation to part n so please watch part n before proceeding with data contracts we've got very limited control over the soap XML request and response messages that are generated use message contracts if you want full control over the generated XML soap messages message contracts can be extremely handy when we want to include some custom data in the soap head up for example example in general soap headers are used to pass user credentials license Keys session Keys Etc message contracts can also be handy when we want to change the name of the wrapper element within the soap message or to remove that wrapper element all together in general use message contracts only if there is a reason to tweak the structure of the soap XML message if all this doesn't make sense at the moment don't worry we're going to look at an example in a bit which should make all this clear we'll be using the same example that we developed within the previous sessions of this video series so the service host is already running and this is the client that interacts with the employee WCF service that we have built so let's request an employee so now a request and a response soap XML messages should be automatically generated and they should be logged as well we discussed logging the messages in the previous sessions of this video series so let's get to the folder where we have these messages logged and let's open the message log file so this is the request and this is the response message let's look at the request message now for better visibility I have copied and pasted this request message on the slide notice that within the soap message we have got a soap envelope and within that we have got a soap header and a soap body within the soap body section notice that we have got this element called get employee this element is called the rapper element look at the name of the rapper element it's get employee this is nothing but the name of the operation contract so within our employee WCF service get employee is the name of the operation contract so by default the rapper element within the soap request message is getting the name of that operation contract and then this I ID element is nothing but the name of the parameter that method expects so ID is the name of the parameter and that parameter is present within that rapper element and we have passed you know one as the value for ID if you look at the response message again we have CAU a soap envelope a header and a body and within the body look at this we have CAU this get employee response again get employee is the name of the operation contract response is is appended at the end of that word so this is the response uh soap message that is sent to the client and within that we have another element called get employee and again here result word is appended at the end and within that element we have got the parameters I mean the properties of employee ID name gender...