Setting WCF DataContract namespace using ContractNamespace attribute

Question

In designing my service, I decided that I wanted to customize the namespaces that appeared in the resulting WSDL.

For the DataContracts, i came across the ContractNamespace attribute which seemed a nice shortcut alternative to setting the same namespace explicitly for every DataContract. My initial attempt looked like this:

[assembly:ContractNamespace("http://types.mycompany.com/2010/08/03")]
namespace MyCompany.MyContracts
{
    [DataContract]
    //...multiple datacontract classes here
}

To my surprise, this did not work. After much tinkering, I was only successful when I finally set the ClrNamespace property of the attribute equal to my CLR namespace (MyCompany.MyContracts in the example). So something like this

[assembly:ContractNamespace("http://types.mycompany.com/2010/08/03",
          ClrNamespace="MyCompany.MyContracts")]

My question is: why did this not work the first way? My expectation was that by not specifying a CLR namepsace, this attribute would affect all datacontracts assembly-wide.

kbrimington · Accepted Answer · 2010-08-04 18:20:35Z

4

If I'm not mistaken, if the ClrNamespace is ommitted, then the contract namespace setting applies to objects in the global namespace.

answered Aug 4, 2010 at 18:20

kbrimington

25.7k5 gold badges67 silver badges75 bronze badges

Sign up to request clarification or add additional context in comments.

1 Comment

Michael Over a year ago

Yeah that clears it up. I was not even familiar with the global namepsace

Collectives™ on Stack Overflow

Setting WCF DataContract namespace using ContractNamespace attribute

1 Answer 1

1 Comment

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

1 Comment

Your Answer

Sign up or log in

Post as a guest

Linked

Related