If you have never worked with PowerBuilder but have been tasked with migrating a decently sized application written in it, I would highly suggest you do the following:
Schedule a meeting with the project owners.
Show up with a blank notebook and pencil / pen.
The first question should be: "What do you want the new system to do?"
Go from there...
Migrating a decently sized system to another language is so full of pitfalls a lot of times it's better to wipe the slate and start over... Unless the team is fluent in BOTH languages. Of course, starting over has it's own drawbacks as well. I hope they are prepared to spend a lot of time and money.;)
subtract the DataWindow.NET suggestion (it's been discontinued in favour of control generation from PB.NET 12.5, which is a little steep in price for custom controls),
then add my opinion that client-server UI design (you don't say whether it's C/S or not, but I'll make that assumption) has different best practices than web design, so a lot of the functionality in the PowerBuilder app should be redesigned for the new platform. (I suggest this to PowerBuilder users even when they're moving to PowerBuilder's WebForms functionality.)
I've seen browsers time out because the developer was loading too many items into a dropdown for a web browser, and while I wouldn't call it optimal for client-server, it didn't bring the UI to a screeching halt.
If you're dead set on this, I'd use your PowerBuilder app as a business definition document, and start budgeting to build from the ground up.
我已将 powerbuilder 12.1 源代码转换为 powerbuilder.net，它为您提供了 Web 环境中的所有功能，但现在它的性能非常慢。
I have converted the powerbuilder 12.1 source into powerbuilder.net it gives you all functionality in web environment but right now its performance is very slow.
经过预测成本审查后，我们决定使用 Visual Studio .NET 重写一个新的表单应用程序，它揭示了正确的选择。
I also did a huge application migration from PB 12.1 to PB.NET. It wasn't easy. I did a heavy use of SetRedraw, and that function is not more available in .NET. After fixing a lot of migrated code, I noticed very low performances compared to PB classic. PB .NET Ide is slower than Visual Studio one, and it allows you to mix PB code with .Net framework code.
After a forecasting cost review, we decided to rewrite a new form application with Visual Studio .NET and it revealed the right choice.
发布评论
评论（4）
如果您从未使用过 PowerBuilder，但负责迁移用 PowerBuilder 编写的大小合适的应用程序，我强烈建议您执行以下操作：
安排与项目所有者的会议。
带着空白笔记本和铅笔/钢笔出现。
第一个问题应该是：“您希望新系统做什么？”
从那里开始...
将一个相当大的系统迁移到另一种语言充满了陷阱，很多时候最好擦掉石板并重新开始...除非团队精通两种语言。当然，重新开始也有其自身的缺点。我希望他们准备好花费大量的时间和金钱。；）
If you have never worked with PowerBuilder but have been tasked with migrating a decently sized application written in it, I would highly suggest you do the following:
Schedule a meeting with the project owners.
Show up with a blank notebook and pencil / pen.
The first question should be: "What do you want the new system to do?"
Go from there...
Migrating a decently sized system to another language is so full of pitfalls a lot of times it's better to wipe the slate and start over... Unless the team is fluent in BOTH languages. Of course, starting over has it's own drawbacks as well. I hope they are prepared to spend a lot of time and money.;)
我建议
我见过浏览器超时，因为开发人员将太多项目加载到 Web 浏览器的下拉列表中，虽然我不会调用它对于客户端-服务器来说是最佳的，它不会使 UI 突然停止。
如果您对此一心一意，我会使用您的 PowerBuilder 应用程序作为业务定义文档，并开始预算从头开始构建。
祝你好运，
特里。
I'd suggest
I've seen browsers time out because the developer was loading too many items into a dropdown for a web browser, and while I wouldn't call it optimal for client-server, it didn't bring the UI to a screeching halt.
If you're dead set on this, I'd use your PowerBuilder app as a business definition document, and start budgeting to build from the ground up.
Good luck,
Terry.
我已将 powerbuilder 12.1 源代码转换为 powerbuilder.net，它为您提供了 Web 环境中的所有功能，但现在它的性能非常慢。
I have converted the powerbuilder 12.1 source into powerbuilder.net it gives you all functionality in web environment but right now its performance is very slow.
我还进行了从 PB 12.1 到 PB.NET 的大规模应用程序迁移。
这并不容易。我大量使用了 SetRedraw，而该函数在 .NET 中并不可用。
在修复了大量迁移的代码后，我注意到与 PB classic 相比性能非常低。
PB .NET Ide 比 Visual Studio 慢，它允许您将 PB 代码与 .Net 框架代码混合。
经过预测成本审查后，我们决定使用 Visual Studio .NET 重写一个新的表单应用程序，它揭示了正确的选择。
I also did a huge application migration from PB 12.1 to PB.NET.
It wasn't easy. I did a heavy use of SetRedraw, and that function is not more available in .NET.
After fixing a lot of migrated code, I noticed very low performances compared to PB classic.
PB .NET Ide is slower than Visual Studio one, and it allows you to mix PB code with .Net framework code.
After a forecasting cost review, we decided to rewrite a new form application with Visual Studio .NET and it revealed the right choice.