Thomas Zang

PBDJ - PowerBuilder Journal Nowadays .NET has become a mainstream programming platform. To be inline with PowerBuilder's .NET deployment and .NET development strategy, the PowerScript language will be enhanced to be a true CLS-compliant .NET language in PowerBuilder 12. Users will be able to consume and extend any CLS-compliant .NET resource, thereby saving them a lot of development time. On the other hand, many modern language features will be brought into PowerScript as well, such as interface and namespace. These features are delivered in a 4GL manner to maintain PB's productivity and bring PowerScript's differentiators to other .NET languages. The original PowerBuilder object model is kept as much as possible to maintain the backward-compatibility; minimize the learning curve; and preserve customers' investment, knowledge, and skills in PowerBuilder. Figure 1 s... (more)

PowerBuilder's .NET Strategy

.NET has become a mainstream programming platform. To be in line with PowerBuilder's .NET strategy (.NET deployment and .NET development), PB11 introduced many .NET-related features: Its .NET compiler enables users to develop .NET Windows Forms (including SmartClient) applications and ASP.NET Web Forms (including AJAX-enabled) applications with functionality similar to PB's native pcode compiler. Its .NET language interoperability feature enables users to consume part of .NET resources in PB .NET targets (Windows Forms or Webs Forms); users can make use of imported .NET types to... (more)