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

I was working on a POC app that integrates a .NET assembly with a PowerBuilder 12.1 WPF app when I ran across this issue. Most anyone doing any assembly integration will discover the same thing. In order to save you some time and bother I’m writing my findings and suggesting a couple of workarounds here. Background One on the key changes to the PowerScript class hierarchy was the insertion of System.Object as the ancestor of PowerObject. Object is now the grand ancestor of all PowerScript Classes. Figure 1 shows that PowerObject now has System.Object members. In object oriented terms this inheritance change means two things. (1) A PowerObject IS A System.Object, (2) A System.Object IS NOT a PowerObject This code is valid PowerObject Lpo System.Object Lso Lpo = CREATE PowerObject Lso = Lpo But this code is NOT valid PowerObject Lpo System.Object... (more)

Release Candidate for Free PowerBuilder .NET Training Video Posted

This week PBDJ will publish part one of a series I am writing called "PowerBuilder .NET RESTful Web Services:  A quick-start how-to guide".   I'm also producing an accompanying video demo series.  To get the buzz going I decided to make each section of the demo video separately available.  When all the pieces are completed I'll tie them all together in a single indexed video tutorial.  The complete video will most probably be published on Sybase.com.  In the first installment, I show the demo program UI and explain the code structure architecture.  Click on this link to watch the... (more)

PB .NET Migration Assistant

PBDJ Blog Post PowerBuilder Developer's Journal - It started off by me wondering, why is there is no version 12 .NET migration assistant like the one in previous versions?  Then it dawned on me. The migration process is its own assistant! Here's what I mean.  The version 12 .NET migration process is significantly different than any migration that came before it.  For the first time in history migration is non-volatile; the original PBLs remain intact and are untouched by the migration process!  Plus, migration creates a new target and source directories and emits migrated source ... (more)

Crazy Eights: Migrating a Legacy Application up to PowerBuilder 12 .NET

I grew up in a Brooklyn NY apartment building. As a young kid, one of my rainy day after-school pastimes was playing card games with the other kids in my building. One of the games we played was crazy eights. If you're curious about this simple card game, check out the Wikipedia description at http://en.wikipedia.org/wiki/Crazy_Eights Recently I was tasked with migrating a legacy application with distant roots in version 4, up to PowerBuilder 12 .NET. The trip over to version 12 Classic went fine with nary a hitch. The ride over to .NET was not too bumpy either. But then I start... (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)