Начнем обсуждение, обмен мнениями, надеюсь, кто-то меня поддержит (Филипп, ASCRUS и т.д.)

Estimated Release: 2009 (“TechWave”, which is usually August)
Migration required: Yes
Upgrade cost: Yes

Announced Features

.NET graphical control integration (i.e. being able to place .NET 3rd party visual controls on WinForms and WebForms windows and user objects, not that there aren’t work arounds for this already with the COM Callable Wrapper)

Managed code in the DataWindow, database drivers, resulting in end-to-end managed code for .NET deployments

.NET Common Language Specification (CLS) support: the ability to produce/consume via PowerScript any assembly that was written in another CLS-compliant language

Complete .NET interoperatbility

WPF Targets

PowerBuilder 12 will introduce a new type of target: the WPF target. Windows Presentation Foundation (WPF) is a new type of .NET application that Microsoft is introducing. While WPF means a lot of things, probably what it is best known for, and what PowerBuilder 12 intends to bring to PowerBuilder developers, are the graphically rich controls. Right now, the most popular representations of this would be the Vista user interface and Office 2007 (think of the “glassy” buttons on the ribbon controls). To get a better idea of what this is and means, see the TechWave 2007 Application Development plenary. This is also a good place to get a taste of the IDE upgrades.

WPF Migration: Because of the distinct change in foundation that Microsoft is providing, there will be challenges to migration. For example, challenges expected at this point include:


changes in available functions, attributes and events in controls,

lack of handles from controls

not all available events in the Win32 model will be available in WPF

As a result, migration to WPF targets will be one-way (you can’t share code between WPF targets and other target types) and there may be some effort required to migrate.

WPF IDE: The IDE for WPF targets will be separate from the traditional IDE that will continue to be used for Win32, WinForms, WebForms, and other types of targets. This new IDE will be based on the Visual Studio shell that Microsoft provides for third parties to leverage. This does not mean that you will be developing PowerBuilder applications in Visual Studio; it means the PowerBuilder WPF Workshop IDE will be using the same shell that is the foundation of Visual Studio. This also does not mean that you will be editing the entire class in one text region as Visual Studio users do. The intention is to not change the way we work in the IDE. This will bring to the table script painter enhancements like:


collapsable code blocks in the script painter

outlining

text markers

updated autoscript

auto-highlighting of matching parentheses

splitter bars

Даже Филипп на Visual Studio (на C#) перешел. Мдя, видимо, не стоит браться за новый
проект на PowerBuilder.

Буду продолжать говнокодить на SharePoint 2007 и BusinessObjects XI...