WCF Service Backwards Compatibility Check?

These situations are solved by integration/regression testing. You write integration tests for initial version and after modifying service to new version you run integration tests again using old client. If they success you didn't break anything.

If they fail you see exactly what calls caused problems.

1 Good point. That would do the trick. If a static check is not possible then a runtime check would be the next best thing.

Thanks – Andy McCluggage Mar 7 at 13:04.

Nothing like that exists Andy but if you get something up and running whereby you have 2 DLLs (one old and one new), you could then use something like BitDiffer to compare them. There was a project on Codeplex that helped with WCF releases, but I can't remember what it is called, sorry. Good luck, -Keith.

Also you may try to compare 2 DLLs using ApiChange, LibCheck or NDepend tools. – aponomarenko Mar 7 at 13:09.

See "Versioning WCF Services: Part I" and "Versioning WCF Services: Part II".

Try to generate unit tests using "Codeplex WCF Load Test" for old interface contract and run them on a new one: This tool takes a WCF trace file and a WCF client proxy, or a WCF interface contract, and generates a C# unit test that replays the same sequence of calls found in the trace file. The unit test can then be used to load-test the target.

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.