我应该从 caliburn 迁移到 caliburn.micro
我正在为目前基于 caliburn 1 的大型项目开发基础设施。
它运行良好，但看起来未来是在 caliburn micro 中，对吗？ 如果我这样做，我该如何实施过滤器？如何指定视图 viewnodel 的视图（非常规）？
放置我的启动逻辑（不是根模型）的最佳位置是什么
I'm developing an infrastructure for a major project currently based on caliburn 1.
It works fine but it seems like the future is in caliburn micro, am I right?
If I do, how do I implement filters? How do I specify view to a view viewnodel (non conventional)?
And whats the best place to put my splash logic (not root model)
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
我建议迁移到 Caliburn.Micro，因为它更简单且更容易扩展。未来的创新都将在这里进行，并且拥有更大、更活跃的社区。就过滤器而言，您实际上可以构建它们并将其插入。请参见此处 Marco 的帖子 您也可以添加非常规视图规范。您只需插入视图定位器并教它如何查找视图。例如，如果您想使用某个属性，您可以让定位器首先查找该属性，如果找到则使用它，否则回退到默认行为。关于启动逻辑，您可以通过自定义 Bootstrapper 来实现。
I recommend moving to Caliburn.Micro as it's simpler and easier to extend. It is where any future innovations will be made and it has a larger more active community. As far as filters go, you can actually build them and plug them in. See here Marco's post You can add non-conventional view specification as well. You just plug into the view locator and teach it how to find views. For example, if you want to use an attribute, you can just have the locator look for that attribute first, use it if found, otherwise fall back to the default behavior. Regarding splash logic, you can do that by customizing the Bootstrapper.