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
Read an interesting article about the .NET Developer Association user group
in Redmond, Washington. You would think that the user group in Microsoft's
backyard (the meetings are held at Microsoft's offices) wouldn't have any
problems lining up guest speakers and drawing a crowd. Well, it looks like
they do because they've had to cancel several recent meetings and have
proposed taking a six-month break to try to determine how to revitalize the
It had me wondering why such a group would have difficulty holding meetings.
Of course, the issue may be specific to that partic... (more)
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
I've written a number of articles in the past on using .NET components, both
visual and non-visual, from a PowerBuilder "Classic" (i.e., Win32)
application. Until now, all of them involved using a .NET component that was
either provided in the .NET Framework or created using Visual Studio. What
changes with PowerBuilder 12 is that we can now write a non-visual component
using PowerBuilder.NET, so the solution is entirely PowerBuilder based.
Technically, this really first became possible with the introduction of the
.NET assembly target in PowerBuilder 11. However, there were a cou... (more)
By the time you read this, PowerBuilder 12.5 should be released. Like several
".5" releases before it (i.e., 6.5, 10.5 and 11.5), this release is a major
release with a number of significant new features. We'll have a number of
individual articles in PBDJ that will dive into these new features in greater
detail. Given the editorial lead time, I wouldn't be surprised if you've even
read a few by the time you read this! For now though, I'd like to give a
brief overview of what you'll see in this new version.
Just to show that you haven't been ignored if you're s... (more)