schema..." />
WCF thinks everything by default is XML so both endpoints will return XML. The second one will return string xmlns="thanksGoofy" rel="nofollow">schemas.microsoft.com/2003/10/Serializat... isn't it If you really want to return just a string, then use Stream as your return type. Or take a look at WCF in .
Net 4. It looks like they made it a whole lot easier to return other types.
WCF thinks everything by default is XML so both endpoints will return XML. The second one will return thanks With the content type application/xml. And if you want POST a string to it, you will have to send it a XML serialized string.
Goofy isn't it. If you really want to return just a string, then use Stream as your return type. Or take a look at WCF in .
Net 4. It looks like they made it a whole lot easier to return other types.
Both methods respond to a POST request on a URI of the format '{BASE_URI}/DoSomething' (just a guess) The first one expects some XML while the second one expects a string (in the body of the HTTP POST request). The first one sends back some XML data () while the second one sends back a string ('thanks') Regarding the 'content-type' setting: application/xml for the first one and plain/text for the second one.
WCF thinks everything by default is XML so both endpoints will return XML. The second one will return.
I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.