How to use namespaces in WCF contracts?

After reading this , this and this I think I understand a little what they mean by contracts of these versions. Is it so that the recommended approach is for my data and message contracts to implement an interface and set DataContract (Name = "SameValue") for different namespaces? Then I would create a new class with the same name and a different contract? If this is correct, it is almost too easy to be true. The reason I'm asking is because I want a smoke test client with a production service and a crash on startup if the contracts are newer than the service.

Does anyone have any additional recommendations / indications?

+3
source share
1 answer

Yes, this attribute allows you to control versions of your contract.

A decent article on best practices for handling changes in WCF .

+2
source

Source: https://habr.com/ru/post/1777036/


All Articles