PowerBuilder 12.5 introduced a number of significant enhancements to web
services support, both for creation and consumption. In particular, the
following were introduced as new features in PowerBuilder.NET:
WCF client proxy WCF service target REST client proxy
We're going to look at what those new features provide and how to use them.
We're also going to look at how we can package some of that functionality so
that it can be used from PowerBuilder Classic applications as well.
Windows Communication Foundation (WCF)
First though, some background. When support for a web service client was
first introduced in PowerBuilder 9, it was done based on an open source
library called EasySOAP. There were some limitations with that
implementation, primarily because the EasySOAP library only supported SOAP
1.1, was limited to XML over HTTP transport, and provided no support for
There's been a lot of discussion since Microsoft's BUILD conference on the
fate of Silverlight. (Something that is an issue for us because Sybase was
originally looking at supporting it for web app development in PowerBuilder
15.) Contrary to what a number of the pundits and would-be pundits have said,
I don't think it's quite accurate to say that Silverlight is dead in Windows
8. I think it's more accurate to say it's evolved.
As background for those who haven't been following this closely, Microsoft
announced that the Windows 8 operating system would support two kinds of
Last month we looked at Microsoft's .NET Pet Shop sample application and saw
how DataWindow.NET technology could be used in the data access layer of an
ASP.NET-based application to reduce the its complexity and increase developer
This month we'll look at another Microsoft sample application to see what
benefits DataWindow.NET technology can provide when used for data
presentation and data access in a Windows Forms (WinForms) application.
To fully appreciate how much DataWindow.NET simplifies the development of
database applications in Windows Forms, you'll need the ... (more)
This two-part article provides a primer on OLE, some practical examples of
its use, and demonstrates some methods for addressing the limitations of
PowerBuilder's implementation of OLE.
In Part 1 I provided some background information for OLE and discussed the
use of custom controls, in Part 2 I talk about OLE Automation and OLE
OLE Automation is the interface through which one application (e.g.,
Microsoft Outlook) makes the methods, properties, and events of its objects
(e.g., Folders, Messages, Address Book) available for use within another
PowerBuilder contains a number of built-in common dialogs that can be used
within your own applications.
What do you do when one of these dialogs meets most, but not quite all, of
the functionality you need? Do you simply accept the limited functionality?
Do you write your own dialog from scratch to replicate them and add the
additional functionality (a maintenance headache)? There is a third option.
You can simply use the dialog that PowerBuilder provides and modify it at
runtime to provide just the additional functionality that you need.
The dialogs PowerBuilder provides includ... (more)