Mixing Message Contract Attributes

re: Mixing Message Contract Attributes

ronjacobs — Mon, 27 Nov 2006 16:46:13 GMT

Nice - but what should you do instead?

New and Notable 128

Sam Gentile — Mon, 27 Nov 2006 18:15:14 GMT

Not too much going on today. Ruby/Rails Rails 1.2 RC1 is out , the first release in almost 8 months.

Dangers of Application Domain Recycling

Nicholas Allen's Indigo Blog — Mon, 27 Nov 2006 19:27:58 GMT

Secure calls to a hosted service are intermittently failing with the following error message: An unsecured

re: Mixing Message Contract Attributes

Nicholas Allen — Mon, 27 Nov 2006 20:12:36 GMT

Ron,

There are two ways to make the operation contract consistent. You can define a message contract for the format of the message that gets sent in response, MyMessageResponse for instance. Or, you can remove the message contract and declare the individual parameters that are being passed.

For instance, this particular example is probably easiest to write like this:

[OperationContract]

string Method(string name);

Table of Contents Scratch Work

Nicholas Allen's Indigo Blog — Mon, 19 Feb 2007 21:46:16 GMT

I haven't forgotten about the goal to put together a table of contents for all of these articles. The

New and Notable 128

Sam Gentile's Blog — Wed, 03 Dec 2008 21:19:25 GMT

Not too much going on today. Ruby/Rails Rails 1.2 RC1 is out , the first release in almost 8 months. The biggest thing seems to be extensive REST support. Here is what is new in ActiveRecord , new in Action Pack and new in Active Support . Blogsphere