更大的 Silverlight 项目实施
随着 Silverlight 应用程序变得越来越大，按功能区域将应用程序分解为单独的较小应用程序以保持较小的总 xap 文件大小是否明智？下载大小是所有 silverlight 开发人员关心的问题，还是因为它可以在客户端下载和缓存的方式而可以？
谢谢。
As Silverlight applications become larger and larger, is it wise to break out an application into separate smaller applications by functional area, to keep the total xap file size lower? Is download size a concern for any silverlight developers, or is it OK because of the way that it can be downloaded and cached on the client?
Thanks.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
看看Prism。密切关注 xap 文件的大小至关重要。作为最终用户，我通常不会等待某些内容加载，我只会转到另一个站点。 Prism 会有所帮助，因为它允许您“轻松”按需加载模块。这包括能够在应用程序启动时或在后台或混合加载“模块”。
Take a look at Prism. Keeping an eye on the size of the xap file is crucial. As an end-user I'm not generally going to wait for something to load, I'll just move on to another site. Prism will help because it allows you to "easily" load modules on demand. This includes being able to load "modules" at app startup or in the background or a mix.
我想说的是，保持每个 XAP 较小有助于提高应用程序的整体性能。我还在大型业务应用程序的某些区域实现了 MEF，用于动态加载 XAP 文件
MEF
您很高兴使用 .Net 4 中的 MEF 作为框架
I would say keeping each XAP small aids in the overall performance of the application. I have also implementation MEF in some areas of a large business application for dynamic loading of XAP files
MEF
You are good to go with MEF in .Net 4 as its in the framework