Welcome!

Helping Developers Master PowerBuilder Classic and .NET

Yakov Werde

Subscribe to Yakov Werde: eMailAlertsEmail Alerts
Get Yakov Werde via: homepageHomepage mobileMobile rssRSS facebookFacebook twitterTwitter linkedinLinkedIn


Top Stories by Yakov Werde

Paul Harvey, the great American radio personality, would always conclude his colorful broadcasts with the quip "And now you know the rest of the story." For those of you not acquainted with Paul's broadcasts, here's a sample. If you get to about 3:40 in, you'll hear the classic remark. Paraphrasing Paul's tag line, in this article you'll learn "the rest of the story" about RAD Development methodology in PowerBuilder 12.5 .NET using a Referenced PB Assembly Target. I'll explain the technique and implementation steps using the open source PEAT PFC demo application. In a previous PBDJ article, "Slicing the Pie with PowerBuilder .NET 12.1 EBF Project Partitioning," I wrote about achieving Classic RAD-like build/test speeds in .NET WPF applications by configuring the Project object partitioning feature. This feature lets you logically carve up a large application into a... (more)

Breaking Platform Limitations

One of the innovative new features in the PowerBuilder 12.5.1 release is its ability to deploy PowerBuilder .NET code to run in 64-bit mode on 64-bit Windows platforms. In this article, after gaining background and perspective on 32- and 64-bit memory management and .NET deployment models, you'll explore the internals, strengths and limitations of this new feature. Introduction Almost all current server, desktop and notebook hardware platforms have 64-bit processors. Almost all current versions of Windows operating systems support both 32- and 64-bit platforms. With the 12.5.1 rel... (more)

Bye Bye SetRedraw( )

A common Classic PB code technique when modifying the displayed contents of window controls, is to turn off screen refresh by calling SetRedraw( false ), performing the update activity and then calling SetRedraw (true). Setredraw( ) is one of those graphic object methods that falls by the wayside when migrating to .NET.  It is no longer supported.  Is this a bad thing that will give your users a migraine headache or a non-issue? This post and the accompanying video will give you a refreshing understanding of the issue and help set your expectations when you migrate and see those ... (more)

Building Bridges: PowerBuilder/InfoMaker Integration in the .NET Universe

There has been some talk lately about the impact of the new .NET PBL and EXE format on applications that dynamically integrate InfoMaker reports (or other external PBLs). The concern is that since PowerBuilder has gone .NET and InfoMaker remains Classic, platform differences will break the integration mechanism that ties these two products together. In this article I'll take a look at the issue, provide some background for the uninitiated and propose a mechanism to bridge the gap. For those of you not familiar with InfoMaker, it's a reporting tool featuring the DataWindow Object... (more)

Migrating Classic Apps That Call Custom DLLs

One difference when migrating Classic Apps between the WinForm/WebForm and WPF is how you need to handle listing referenced DLLs during the migration process.  In .NET the deployer copies referenced Non System (those not part of Windows) DLLs into the OUT folder together with the executable and other references.  The .NET project object must have a listing of required DLLs.  In Win/Web Form migration, the migration wizard has a page on which you list Referenced DLLS.  The wizard actually scans your code and lists any Non System DLLs it finds referenced in external function calls ... (more)