Mvvm跨命名约定 [英] MvvmCross Naming Conventions

问题描述

我对MvvmCross还是很陌生，并且了解成功使用框架取决于某些领域的特定命名约定.我一直在寻找有关这些命名约定的信息，但是除了从观看各种视频中找出其中的一些约定外，我还找不到一处可以解释所有要求的内容.有什么建议吗?

I'm pretty new to MvvmCross and understand that successful use of the framework relies on specific naming conventions in some areas. I have been looking around trying to find information on these naming conventions, but apart from figuring some of them out from watching various videos, I haven't been able to find anything that explains all the requirements in one place. Any suggestions?

推荐答案

使用的命名约定:

绑定中的
• 在 https中: //github.com/MvvmCross/MvvmCross/wiki/Customising-using-App-and-Setup#registering-custom-bindings
• 在View-ViewModel查找中位于 https://github.com/MvvmCross/MvvmCross/wiki/Value-Converters#referencing-value-converters-in-touch-and-droid

• in bindings are in https://github.com/MvvmCross/MvvmCross/wiki/Customising-using-App-and-Setup#registering-custom-bindings
• in View-ViewModel lookup are in https://github.com/MvvmCross/MvvmCross/wiki/Customising-using-App-and-Setup#overriding-view-viewmodel-associations
• the default IoC setup - using the postfix "Service" is described in https://github.com/MvvmCross/MvvmCross/wiki/Service-Location-and-Inversion-of-Control#bulk-registration-by-convention
• the registration of ValueConverters is described in https://github.com/MvvmCross/MvvmCross/wiki/Value-Converters#referencing-value-converters-in-touch-and-droid

MvvmCross宣言- https://github.com/MvvmCross/MvvmCross/wiki/The-MvvmCross-Manifesto -不会强制您使用任何这些约定-您可以覆盖此约定并使用自己的约定方案，或者对想要执行的任何操作使用不同的机制.

The MvvmCross manifesto - https://github.com/MvvmCross/MvvmCross/wiki/The-MvvmCross-Manifesto - doesn't force any of these conventions on you - you can override this and use your own convention schemes or use your a different mechanism for anything you want to do.

这篇关于Mvvm跨命名约定的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！