I don't share the other answerers inclinations to use RIA Services for WPF without having an actual RIA Services client: If you don't use an actual RIA Services client compontent as they recommend, that would usually mean rewriting large parts of your data handling code on the client anyway.
Usually, the auto-generated classes are in a RIA Services app are used everywhere, and their behavior isn't easily remodelled. In fact that would be really, really difficult to do and you would be better off to just rewrite most of the thing. Does your app, for instance, not does binding a save button's Disabled
property to XyzContext.HasChanges
?
If your app is typical, you really need the real RIA Serives client for a clean port.
Semi-luckily, RIA Services has gone open-source, and WPF support is on their roadmap: OpenRiaServices.
I never used it, and I sense progress on that is a bit slow, but, dending on your own inclinations, it may be a realistic option to use that. You will just have to expect to be a bit on your own by doing it.
Also, do you use any third-party libraries that dependend on RIA Services? For example, if you use DevExpress, you will also have to port their components that use RIA Services (RiaInstantFeedbackDataSource
, etc.).
If you try it, drop a comment on how it went. I have a RIA Services application about the same size myself.