将Powerbuilder 9应用迁移到12 [英] Migrating a Powerbuilder 9 app to 12
问题描述
我最近开始支持PowerBuilder 9应用程序，该应用程序最终已升级到PowerBuilder12.我试图弄清楚我是否应该考虑迁移到PowerBuilder Classic或.NET.在我看来，使用PB.NET可以为我提供更大的灵活性，但是阅读文档并不能使我清楚地了解会有什么好处.显然，我可以利用WPF表单，并且可以使用Visual Studio Shell，但是我不知道这些是否足以更改.
好问题，而不是琐碎的问题.
从正面看，您可以获得WPF控件和布局控件.如果您是不打算走得太远的开发人员，那将使您获得漂亮，闪亮的控件，可蒙皮性以及内置在画家中的调整大小/缩放比例.如果您是超级怪胎，则可以开始进行嵌入控件之类的操作(例如，控件按钮内的进度条代表按钮上的倒数计时器，这是在定时对话框中时间耗尽时的默认操作) )，尽管当您和PB都尝试使用XML做一些花哨的事情时，我猜测您可能会不时踩到彼此的脚趾.
此外，除了PowerScript之外，您还可以轻松访问庞大的.NET函数库.再说一次，随和的开发人员可能不会从中获得太多好处，但是从鼻子到屏幕的类型将使他们轻松地在他们的应用程序中内置SMTP功能.
从负面来看，您可能会指望迁移不会像PB到PB迁移那样顺利.如果您明天需要它工作，那么今天从PB到PB.NET的迁移可能就不可行了.有些东西会坏掉，需要修复，每个窗口都需要动手才能至少利用调整大小的优势.
我发现的另一个缺点是性能，特别是应用程序启动(我听说这是WPF开发人员(而不仅仅是PB.NET开发人员)的共同抱怨).我原本以为一切都会更快，但是发现它实在是一团糟.
另外一点:最新的PB(在撰写本文时)为12.6，这是12.5的维护补丁.如果您购买12.0，将无法免费升级； 12.0和12.5之间的转换是一个主要"版本，需要进行价格昂贵的升级.也许您想要 n-1版本，但如果不是，则将购买目标定为12.5.
祝你好运.
@Matt Balent间接在评论中提出了另一个要点.从PB9迁移到PB12，如果您是经验丰富的PB开发人员，则可以在同一天保持高效，而不会错过任何拍子.转向PB.NET将带来不平凡的学习曲线. IDE有很大的不同，因此即使第一天在CommandButton上设置Default属性也可能令人沮丧(...并非没有可能，但是如果这是您的第一项任务，我计划30分钟而不是30秒).
I've recently started to support a PowerBuilder 9 app which is finally being upgraded to PowerBuilder 12. I'm trying to figure out whether I should be looking at migrating to PowerBuilder Classic or .NET. It seems to me that going with PB.NET would give me more flexibility going forward, but reading the documentation doesn't give me a clear picture of what the benefits would be. Obviously, I'd be able to take advantage of WPF forms, and I'd be using the Visual Studio Shell, but I don't know if those are good enough reasons to change.
Good question, and not a trivial one.
On the plus side, you get WPF controls and layout control. If you're a developer that isn't planning to go too far afield, that will get you pretty, shiny controls, skinability, and resize/scaling built into the painter. If you're an uber-geek, you can start doing things like embedding controls (think a progress bar inside a control button to represent a count-down timer on the button that will be the default action when time runs out on a timed dialog), although when both you and PB are trying to do fancy things with your XML, I'm guessing that you might step on each others' toes from time to time.
Also, you get easy access to the vast .NET library of functions, in addition to PowerScript. Again, the easy-going developer may not get much advantage out of that, but the nose-to-the-screen type will get a kick out of easily building SMTP functionality into their app.
On the down side, you can probably count on the migration going not quite as smoothly as a PB to PB migration. If you need it working tomorrow, starting on a PB to PB.NET migration today probably isn't the way to go. Some things will break and need fixing, and every window will need hands on to at least take advantage of the resizing.
The other down side that I found was performance, particularly app start up (and I hear this is a common complaint among WPF developers, not just PB.NET developers). I was expecting everything to run faster, but found it to be a mixed bag.
One other point: The latest PB (at time of writing) is 12.6, which is a maintenance patch of 12.5. If you buy 12.0, you won't be able to upgrade for free; the jump between 12.0 and 12.5 is a "major" release that requires a priced upgrade. Maybe you want the n-1 version, but if not, target buying 12.5.
Good luck.
@Matt Balent indirectly brought up another good point in the comments. Moving from PB9 to PB12, if you're an experienced PB developer, you can probably be productive the same day without missing a beat. Moving to PB.NET will entail a non-trivial learning curve. The IDE is significantly different, so even setting a Default attribute on a CommandButton on the first day may be frustrating (... not impossible, but if that's your first task, I'd plan 30 minutes instead of 30 seconds).
这篇关于将Powerbuilder 9应用迁移到12的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
