如何：多屏幕/区域Silverlight应用程序？
我现在必须使用 MVVM 创建一个多屏 Silverlight 4 RIA 应用程序。
每个屏幕都必须划分为多个区域（例如主从场景，而每个屏幕都是不同的部分，并且一个可以控制另一个区域）。
您能给我一些想法来实现这样的应用程序的正确方法是什么吗？
棱镜是正确的选择吗？我开始阅读 Prism 手册，非常喜欢以非常灵活的方式切换区域和屏幕并进行控制的想法，但是，如上所述，我发现将其拆分到许多组件上太过分了。
如果 Prism 是正确的选择，那么我将不胜感激任何类型的指导或对这个特定场景的指导的参考（多个屏幕和区域，并且 OTOH 没有让我的解决方案在无数的项目中被发现。
I have to create now a multi-screen Silverlight 4 RIA application with MVVM.
Each of these screens has to be devided in multiple regions (for example master-detail scenario whereas each of them is a different section and one has control on the other).
Can you give me some ideas what should be the right way to implement such an application?
Is Prism the right choice? I started reading the Prism manual and liked very much the idea of having regions and screens switched and controls in a very flexible manner, but, as said above, I find it too overkill to split it all over many assemblies.
If Prism IS the right choice, then I would appreciate any kind of guidance or reference to guidance on this particular scenario (multiple screens & regions and OTOH not getting my solution spotted with a gazillion projects.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
我相信 PRISM 是构建具有多个区域和视图的应用程序的正确选择。您可能会说这几乎就是复合应用程序的定义。
但我还要记住，您不必使用 PRISM 拥有的所有组件，您可以挑选。我建议您考虑 PRISM 和测试/原型的各个方面，以确保您对所提供的设施感到满意。在我构建的一个大型应用程序中，我使用了 PRISM，但经过一些原型调查后，我只使用了 EventAggregator 和模块化功能。
我选择不使用区域支持，因为我发现在 Silverlight 中使用 ItemControl 和 ContentControl 组件使我能够将视图和部分视图注入到我的界面中。
我发现 ASP.NET MVC 的经验在考虑如何将 UI 协调/分解为部分视图时非常有用。
希望有帮助。 Stocktrader 应用程序是一个很好的学习示例（包含在 PRISM 发行版中）。
I believe that PRISM is the correct choice for building an application with multiple regions and views. You could argue that that is almost the definition of a composite application.
But I would also remember that you don't have to use all the components PRISM has, you can pick and choose. I would recommend that you consider each aspect of PRISM and test/prototype to ensure you are happy with the facilties offered. In a large application I have built I use PRISM but after some prototype investigations I only used EventAggregator and the Modularity capabilities.
I chose not to use the region support as I found working with ItemControl and ContentControl components in Silverlight gave me the ability to inject views and partial views into my interface.
I found experience from ASP.NET MVC proved useful in considering how to coordinate/break up my UI into partial views.
Hope that helps. The Stocktrader application is a great example to learn from (included with the PRISM distributable).