A small, yet powerful framework, designed for building applications across all XAML platforms. Its strong support for MV* patterns will enable you to build your solution quickly, without the need to sacrifice code quality or testability.
MyNamespace.Views.StudentViewModel.
locate to:
MyNamespace.Views.StudentView.
locate with context (Details):
MyNamespace.Views.Student.Details.
It just work with a string 'Details', so why use object type?
A question that was raised a long time ago: It pollutes the name definition.
I must def a namespace like 'xxx.Student.xxx'. But I also have a model named 'xxx.Student.cs'. It's weird to reference members. 'Student' is a class, and also is namespace.
MyNamespace.Views.StudentViewModel. locate to: MyNamespace.Views.StudentView. locate with context (Details):
MyNamespace.Views.Student.Details.
It just work with a string 'Details', so why use object type?
A question that was raised a long time ago: It pollutes the name definition. I must def a namespace like 'xxx.Student.xxx'. But I also have a model named 'xxx.Student.cs'. It's weird to reference members. 'Student' is a class, and also is namespace.