将 CAB 和 Prism 2 升级到 Prism 4
我们有几个 CAB 和 prism 2 应用程序，计划迁移到 Prism 4。
有人有将 CAB 和/或 Prism 2 应用程序迁移到 Prism 4 的经验吗？
- 有什么我们应该注意的“陷阱”吗？
- 您如何估计迁移？例如，原始开发成本的 x% 或每个屏幕工作的 y 小时。
We have several CAB and prism 2 applications which we plan to migrate to Prism 4.
Has anyone any experiance with migration of CAB and/or Prism 2 applications to Prism 4?
- Are there any "gotchas" that we should be aware off?
- How would you estimate the migration? Would for example x% of original development cost or y hours per screen work.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
我刚刚升级了一个大型（30 个模块）Prism 2 应用程序。总共花了大约一天的时间，但大部分时间都花在更改命名空间和引用上。我按照 Microsoft 提供的信息进行操作升级。将 DI 保留为 Unity 使该过程变得更加容易，如果我从 Unity 迁移到 MEF，可能会花费更长的时间。我还没有遇到任何“陷阱”，如果/当我这样做时，我会更新这个答案。
值得注意的是命令的更改，否则您将遇到 InvalidCastException，DelegateCommand 的 T 不是对象也不是 Nullable。
I have just upgraded a large (30 module) Prism 2 application. It took about a day in total, but most of that time was spent changing namespaces and references. I followed the information Microsoft supplied when upgrading. Leaving the DI as Unity made the process much easier, it would have probably taken much longer if I had moved from Unity to MEF. I've yet to hit any "gotchas", will update this answer if/when I do.
It's worth noting the changes to commands otherwise you will come across InvalidCastException, T for DelegateCommand is not an object nor Nullable.