locked
Support for ServicedComponents lacks versioning RRS feed

  • Question

  • It is not really feasible to version ServicedComponents. Unless you update *all* dependent clients a version change of a ServicedComponent is a nono. If the interface stays the same you better not re-version your ServicedComponents as this will breach compatibility. Therefor releases of new ServicedComponents is not support by the .NET framework.

     

     

    Tuesday, June 24, 2008 11:26 PM

All replies

  •  

    That's rather the point of the contract, to "guarantee" that both sides know what they should do. If that changes then you either version (create a new) the contract or draw up a new contract and everyone needs to change. There's no mystery there. I have argued on this forum before that this isn't a very practical situation http://forums.microsoft.com/msdn/ShowPost.aspx?PostID=3141067&SiteID=1

     

    but I don't think I'd go as far to say that Serviced Components are not supported by .net.

    Sunday, June 29, 2008 3:01 PM