PowerBuilder TV Webcast: Bootstrap for PowerBuilder

Bootstrap for PowerBuilder
Presenter: Roland Smith
Tuesday, October 4, 2016 at 8:00 AM PDT (Los Angeles) / 17H00 CEST (Paris)

Download the source files of a PBT from your source control system and import the objects into empty library files that it creates for you. Follow that up with any rebuilds and regenerates that are needed to get all objects to compile successfully. With PowerBuilder Bootstrap:

• Extract all source code files for a target from a source control system
• Create new library files for a target and import all the object source code files
• Generate a new PBC file for a workspace
• Optimize all libraries for a target
• Compile the executable files for a target and copy to a deployment folder

PowerBuilder TV Webcast: PowerVCS

PowerBuilder Version and Source Control with PowerVCS
Presenter: Phil Wallingford
Tuesday, September 20, 2016 at 8:00 AM PDT (Los Angeles) / 17H00 CEST (Paris)

A web-based solution where repository data resides on a secure Web server and source control functions are accessible with a browser. For those of you who have reached the limits of “PBNative”, who miss Object Cycle, or who have yet to implement a source control system of any description. See how PowerVCS is an ideal solution for locally and geographically distributed development teams.

Future of PowerBuilder webcast - Part 5 - Low Level Roadmap

Part 5 of the Future of #PowerBuilder webcast (Low Level Roadmap) starts at 9:00 AM PST tomorrow (July 28th). If you have not already signed up, you can still do so at http://www.appeon.com/form/form.php?mid=20

PBNISMTP update

I created a 12.6 build of PBNISMTP back in April of 2015 but never updated the downloads or source code.  That's been corrected.

More recently, I moved the project to VS2015.  It has also been updated to the most recent version of CPJNSMTPConnection (3.17). The VS2008 code is still available but will no longer be maintained.

Since CPJNSMTPConnection is dependant on CWSocket I updated that to the latest version as well (3.17),  The new version on CPJNSMTPConnection also no longer references OpenSSL, but instead uses SSLWrappers  and CryptoWrappers

I did have to make one minor change to CWSocket. For some reason, CPJNSMTPConnection was still calling a Delete method on CWSocket that had been removed in the latest version. I added a noop Delete method so that the code would continue to compile.

The only PowerBuilder sample provided is for PowerBuilder 12.6. If you want to use the utility with an earlier version of PowerBuilder you will need to download the C++ source and compile it referencing the PBNI/SDK files for that release.

Note that the PBX files are significantly larger than they were when VS2008 was used to compile them. That's because of a change that Microsoft made in the way files that dynamically link to MFC are compiled starting in VS2010.

Using the XMLSerializer rather than the DataContractSerializer in PowerBuilder.Net WCF web services

By default, WCF services use the DataContractSerializer.   PowerBuilder Classic using ASP.Net web services, which only support the XMLSerializer.  Therefore, if you create a WCF web service using the default settings in PowerBuilder.Net you won't be able to call it from PowerBuilder Classic.

WCF services can be configured to use the XMLSerializer instead.  To do that for PowerBuilder.Net
you'll need to add that option to the WCFAttributes.xml file that PowerBuilder uses to display the options in the IDE.  You should find it in the following location:

<system drive>:\users\<username>\AppData\Local\Sybase directory.

If you add the following into the <Service Attributes> entries:

<ServiceAttribute Name="XmlSerializerFormat"></ServiceAttribute>

Then it will appear in the IDE and you can check it.  Then regenerate the service.  It will now use the XMLSerializer.  At that point you can call it using the PowerBuilder web service client and/or the web service based DataWindow.

Interesting .Net statistics

Telerik's 2016 .Net Developer Report is out.

SDTimes notes that the majority of respondents are using WPF now (46% versus 42% for Windows Forms).  Windows Universal Platform is currently in use by less than 10% of respondents.

Recap of PowerBuilder Future Webcast 4

The recording of the 4th webcast (and the previous 3) can be found at: www.tinyurl.com/newroadmap

This webcast was the high level roadmap.  Normal legal disclaimers apply.