A Modern light-weight MVVM framework based on RX and Await
The developer of this repository has not created any items for sale yet. Need a bug fixed? Help with integration? A different license? Create a request here:
MVVM-Sidekick: A Modern light-weight MVVM framework based on RX and TAP await. The CORE of this framework is ViewModelBase Class which you can even use it with other frameworks.
The aim of this project: This project has learned a lot of good ideas from Prism and Reactive UI/Command project, and it is using new techs offered by .Net 4.5 and Windows Run-time. It offers a suitable foundation for new tech environment, based on cool ViewModelBase and ReactiveCommands.
项目的目的：集合 Reactive UI/Command, Prism 等框架的优点，应对.Net 4.5 和 Windows Run-time 带来的变化，为新技术环境量身打造一套以 ViewModelBase/ReactiveCommand 为核心的基础。
MVVM-Sidekick is design on Windows 8 Modern Style Apps, and we got that ambition to cover all modern XAML run-time.
本框架从设计开始就以Windows 8 Style App作为运行环境进行测试，野心覆盖所有XAML运行环境。
F.A.Q. 请戳 这边
Open source projects
Close source projects
Full support for Data Contract Serializing. You can easily save your status of View Model to JSON or XML stream, and easily restore from, too.
全面支持Data Contract序列化 可以将一个VM的全部状态用任何方式保存为JSON/XML,反序列化后只需要简单操作就可以恢复工作
This is light-weight framework. You can use our dll or use code file, either way you just need to install Reactive Extensions with Nuget.
Each of Model Properties in MVVM-Sidekick has it's own event container, can subscribe or broadcast it self. LinQ-Like code with RX can be used.
Model所有的成员都有自己的事件容器，可以独立与其他事件订阅与广播。可以使用 LinQ-Like 语法进行配置和订阅。
You can configure business logic of your properties and commands where they were declared. This will avoid your jumping between different parts in one View Model code file. (This kills me when I was working with other frameworks: for example you cannot configure a
DelayCommandat the Property/Field declaration because “this” instance is not ready yet .)
You can also separate the business logic to your View Model declaration into a decorator factory or something else, to manage all code involved one same USE CASE together, with the sequence same as document you a following. You can also easily add more business logic anywhere you like.
In Nuget folder
See document: Hello world
More document would be here in Onenote form: https://onedrive.live.com/redir?page=view&resid=45FE30D49807DF3C!1002973&authkey=!AL4aMWuTcP8yEEw