Branch 5 supports all clients including Silverlight, however there will be breaking changes between Branch 4 and Branch 5. Branch 4 is designed to have minimal breaking changes so that at any time, even a few years from now, someone using WCF RIA Services can swap over to Open RIA Services with little to no breaking changes. Basically, Branch 4's purpose is to be life support for existing Silverlight applications.
What we are doing with Branch 5 is porting the existing Silverlight native client over to Portable Class Library. That is what will allow us to support everything from Silverlight to Mono. There will need to be environment specific implementations of some code which isn't supported by the PCL but nothing that needs to be generated.
I need the multiplatform support as described in this branch 5 for Mono, WinRT and (Something for desktop (Currently using Silverlight) for pre WinRT Clients).
Will there be an Silverlight Proxy for branch 5 as well and will it have the same functionality than the current RIA WCF Service proxy have.. ( Client Side Change Tracing ,Client Side validation.)
If you say I must use branch 4 for SL. Then I will end up having to use both Branch 4 and 5 at the same time. And if there Client side proxy's are not generated in the same way I cannot do code reuse across my clients, my most important long term goal. So I don't think this is an option.
Any suggestions ?
So as soon as Branch 5 is Stable I can move over from Branch 4 to Branch 5 and from there one I will have an single Platform on my clients for SL/MONO/WinRT..
That is exactly what I wanted, Now I can Invest into this and have a single codebase for all my clients. Perfect
Then we can use RIA Services on Windows Phone.