Helping Developers Master PowerBuilder Classic and .NET

Yakov Werde

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

Top Stories by Yakov Werde

Among PowerBuilder 12.5 .NET's new features comes the ability to use WCF to call RESTful web services. This article, the first in a two-part series, provides a PowerBuilder 12.5 .NET developer with the foundational knowledge and skills to rapidly get up and running building PowerBuilder RESTful Web Service clients. Along the way I'll share with you a few tips and workarounds. Introduction PowerBuilder 12.0 .NET provided the ability to call SOAP-based web services using Microsoft's .NET 3.5 WCF API. I encourage those of you not familiar with WCF and SOAP to view my PowerBuilder WCF primer and StockTrader reference application overview hosted on You can get to all my free tutorials from New with version 12.5, along with an upgrade to WCF 4.0, is the ability to call RESTful web services, an increasingly popular m... (more)

A Sane Way to Code DataObject Result Set Definitions in Syntax Mode

One of the minor DataWindow Object design annoyances I have accepted as a fact of life is the total lack of tool support when writing a SQL Select statement in Syntax mode.  I'm often forced into syntax mode by limited abilities of the GUI SQL painter.  In support what I imagined was my own personal preference, I have noticed over the years that many developers prefer typing SQL in syntax over using a graphical interface to generate their code.  It's often more than personal preference that drives me into sytax mode, just ask anyone who has watch their hand coded SQL get mangled ... (more)

PowerBuilder 12.1 .NET IDE Productivity

I recently migrated a Classic MDI application to .NET.  One of the nice features that helped me prepare my code for .NET deployment is the Unsupported Feature list that appears in a selectable view in the Output window.   That view gets populated following a build if the app has unsupported features.  The unsupported list is a very useful guide to locating and navigating to lines of code and property references that need your special attention.  Here's what it looks like: While working my way through the code I noted that some unsupported features are innocuous.  The PowerScrip... (more)

Peering Behind the PowerBuilder .NET Assembly Curtain

Part of the allure of the .NET platform is that all code, no matter what language or grammar it's written in, compiles down to Common Intermediate Language (CIL) that is managed and executed by the Common Language Runtime (CLR). PowerScript code goes through a two-step process before becoming CIL. First it's run through PBCS.exe, which converts PowerScript to the equivalent C#. Then the emitted CS code is compiled by the C# compiler, CS.EXE, into standard CIL. One of the tools that ships with the .NET SDK is a CIL disassembler ILDASM.exe. The tool allows you to explore the emitt... (more)

Jim O'Neil on PowerBuilder and the Cloud

Filmed by yours truly live at the Connecticut PowerBuilder User Group meeting February 2011. This was a great presentation by the master Jim O'Neil.  We were all thoroughly engaged in the content and learned a lot.  I'm sure you will too.   ... (more)