1 Answer, 1 is accepted
0
Hello Mauro,
Let me make a quick clarification. The PersistanceFramework is designed to persist control specific properties, only. Basically, you are not allowed to persist properties defined in your View-Model because you can use different approaches to save your View-Models.
Regarding the implementation, it is straightforward and you can use one of the approaches described in this article. Furthermore, you can take a look at this online demonstration project and see how we implemented the ICustomPropertyProvider in order to implement custom persist logic.
Furthermore, you can find ready to run projects, that can be used as start-up projects, in our XAML SDK.
Regards,
Pavel R. Pavlov
Telerik
Let me make a quick clarification. The PersistanceFramework is designed to persist control specific properties, only. Basically, you are not allowed to persist properties defined in your View-Model because you can use different approaches to save your View-Models.
Regarding the implementation, it is straightforward and you can use one of the approaches described in this article. Furthermore, you can take a look at this online demonstration project and see how we implemented the ICustomPropertyProvider in order to implement custom persist logic.
Furthermore, you can find ready to run projects, that can be used as start-up projects, in our XAML SDK.
Regards,
Pavel R. Pavlov
Telerik
TRY TELERIK'S NEWEST PRODUCT - EQATEC APPLICATION ANALYTICS for WPF.
Learn what features your users use (or don't use) in your application. Know your audience. Target it better. Develop wisely.
Sign up for Free application insights >>
Learn what features your users use (or don't use) in your application. Know your audience. Target it better. Develop wisely.
Sign up for Free application insights >>