Do I have to be careful about getting new versions of WCF like I was with COM?

[NewsBot]

I’m working on my first WCF application, and in many ways I am reminded of when I worked with COM+ and before that MTS with VB6.* With VB6 if I made modifications to the code of public method, properties or events, and compiled the COM+ app, then it could be put in place without any problem (assuming of course that I hadn’t made any mistakes, etc).* However, if I added or removed a parameter to any public method, property or event, or if I added a new public method, property or event, or removed a public method, property or event, then it would break what is known as binary compatibility.* Recompiling the COM+ app would generate a new GUID and any other application which used that COM+ component would have to be adjusted to be aware of the change.

 

I am wondering if there is any analogous idea with WCF services.* My normal way of doing development will be to write a few methods for the WCF service, compile it and make it available, and then write some simplistic test bed app to test what I’ve done.* I realize that my question really exposes my ignorance of WCF, but I’ve got to know if compiling a WCF with a set of OperationContracts at one point, and then adding more later, will mean I’ve got a new WCF service which any application using it would have to be updated to utilize it.* Is it somewhat analogous to “breaking binary compatibility”?

 

 

More...

 

View All Our Microsoft Related Feeds