If you've been following the product direction for PowerBuilder for the last few releases, and particularly with respect to the upcoming PowerBuilder 12, you know that PowerBuilder is evolving into a .NET development tool. As PowerBuilder developers, you'll also know that the key strengths of the product are its productivity through Rapid Application Development (RAD), support for object-oriented programming (OOP), and simplified data access and update through the DataWindow.
PBDJ article, by Bruce Armstrong

---

PowerBuilder 12 Getting Started Guide
http://infocenter.sybase.com/help/index.jsp?topic=/com.sybase.infocenter.dc37772.1200/html/pbgs/title.htm

PowerBuilder 12 User Guide
http://infocenter.sybase.com/help/index.jsp?topic=/com.sybase.infocenter.dc00844.1200/html/pbug/title.htm

PowerBuilder 12 Deploying Applications and Components to .NET
http://infocenter.sybase.com/help/index.jsp?topic=/com.sybase.infocenter.dc00586.1200/html/dplynet/title.htm

---

PowerBuilder 12 has been released, and if you've been paying attention, you know that it now comes in two flavors! There's PB12 Classic for traditional Win32, WinForm, WebForm, .NET Assembly, and J2E component targets, and PB12 .NET for WPF (Windows Presentation Foundation) and WCF (Windows Communication Foundation) proxy targets.

---

This reference application highlights PowerBuilder 12.0's abilities as both a development environment and a runtime platform for rich and thin clients. The PowerBuilder clients are delivered in four versions; Classic Win32, .NET Win Form, .NET Web Form and .NET WPF WCF. These client applications illustrate how you can leverage PowerBuilder's enterprise .NET APIs, DataWindow Technology, and the PowerScript coding language in a developer-friendly and productive IDE to rapidly build Microsoft-compatible client applications.
Solution Samples, Sybase

---

While at one point their may have been doubts regarding the continued success of PowerBuilder, the release of version 11 showed that PB is here to stay. PowerBuilder 12 was released a few days ago and it has a bright future ahead. Help us to keep monitoring the behaviour of PowerBuilder developers in the coming year.

Take the Novalys PowerBuilder survey 2010 and find out what are the most awaited developments of PB? What proportion of PB teams adopted .NET technology in 2009? Who's still using PB5? Who has moved to PB11? Where do you fit in?

---

The migration march to PB 12.NET will have many shops revisiting legacy applications. In this article I'll show you a technique to use for rolling multiple test cases into a single test suite and how to approach writing test cases that exercise database-centric code..

---