Microsoft Dynamics (Axapta) 升级
我想将 Axapta 从版本 2.5 升级到 3.0 或 4.0(待考虑)。 可能不会那么难,但我的版本有很多定制代码 - 新类、数据源、表单等,我不知道需要多少时间。 您有从2.5升级到3.0或4.0的经验吗? 移动或重写新 Axapta 版本中的所有更改有多困难? 我将感谢任何形式的帮助。
I'd like to upgrade Axapta from version 2.5 to 3.0 or 4.0 (to be considered).
Probably it wouldn't be so hard, but my version has A LOT of customized code - new classes, data sources, forms, etc. and I have no idea how much time can it take.
Do you have any experience with upgrading from 2.5 to 3.0 or 4.0?
How difficult may it be to move or rewrite all changes along with new Axapta version?
I'll be thankful for any kind of help.
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(1)
首先,我想知道为什么您考虑升级到 Axapta 3.0(从 2002 年 10 月开始)或 Axapta 4.0(从 2006 年 3 月开始),因为现在有 AX 2012 等更新的替代品可用。
元素类型
一般来说,新元素(表单、类等)在升级时只会带来一些小问题。修改元素会更加耗时。数据结构的变化也可能带来挑战,因为它可能需要重写。报告的升级可能非常耗时。应始终考虑对元素进行完全重写,有时会更快。
比较过程
当您使用比较工具(两次)时,单个修改元素的升级过程通常很简单。将旧图层与旧原始图层进行比较,并将新图层与新原始图层进行比较。修改应该或多或少匹配。
估算报告
AX 2009 提供了位于工具\开发工具\代码升级\估算报告中的估算报告。时间估计基于升级某些代码冲突的估计平均时间(在参数中设置)。
我之前没有接触过该报告,但任何估计都不确定,至少有 50%。
Fist off, I wonder why you consider to upgrade to Axapta 3.0 (from Oct 2002) or Axapta 4.0 (Mar 2006), when there is newer alternatives like AX 2012 available right now.
Element types
Generally new elements (forms, classes etc.) poses only minor problems when upgrading. Modified elements are much more time consuming. Data structure changes may also pose challenges as it may require rewrites. Reports may be very time consuming to upgrade. A total rewrite of an element should always be considered, it is sometimes faster.
Compare process
The upgrade process for an individual modified element is usually straightforward when you use the compare tool (twice). Compare your old layer with old original layer, and compare new layer with new original layer. The modifications should match more or less.
Estimation report
AX 2009 provides an estimation report located in Tools\Development tools\Code upgrade\Estimation report. The time estimate is based on an estimated average time to upgrade certain code conflicts (setup in the parameters).
I have no prior experience with the report, but the any estimate is uncertain with 50% at least.