We're looking to build mobile apps (in addition to our existing WinForms app) using Xamarin and our CSLA objects, and we'd like to continue using the mobile object concept (so binding our existing Csla objects to the XAML Xamarin forms).
One thing I'm concerned about though is the server side of the of mobile objects if we make changes to the CSLA object, such as adding or removing a property or even a child object / collection.
We can't force everyone to update at the same time, and it make take time for the app to even be available in the store after its approved. Meanwhile the currently deployed version will need to work, so I'm wondering what the recommendation is to handle this. Deploy a new data portal host site for the new version, while leaving the old one intact? That seems like it would make breaking DB changes more difficult to handle. Somehow handle the differences in code? Any advise would be great!
