PowerBuilder 11 deploys entire applications as .NET Windows Form or Web Form
applications and deploys individual components as .NET Assemblies and as .NET
Web Services. Version 11 consumes resources of the default .NET framework as
well as resources of custom developer-defined .NET resources.
Non-PowerBuilder .NET solutions can interoperate with, and take advantage of,
the unparalleled productivity of PowerBuilder’s data access and data
manipulation capabilities. In short, PowerBuilder 11 creates as well as
consumes .NET resources.
Once PowerBuilder 11 has deployed an application or a component as .NET, the
developer can begin taking advantage of external .NET resources on a scripted
basis through PowerScript enhancements. The scripted .NET interoperability in
PowerBuilder 11 is predicated on a new conditional compilation feature.
Conditional compilation allow... (more)
In June of 2007, Sybase released PowerBuilder 11. PowerBuilder developers can
now deploy PowerBuilder components as .NET Assemblies or as .NET Web
Services. A PowerBuilder developer can now create these .NET resources so
that those who develop .NET solutions can benefit from PowerBuilder and
DataWindow productivity regardless of what development tool they use.
PowerBuilder 11 also gives its users the ability to deploy entire
applications as ASP .NET Web Forms applications (WebForm) as well as to
deploy entire applications as .NET Windows Forms (WinForm) applications.
This article will talk first about what constitutes a .NET Smart Client, its
attributes, its behaviors, and then we'll talk about how the Intelligent
Updater feature fits into PowerBuilder 11's .NET Smart Client support
initiative. Finally, we'll walk through a detailed tutorial on how you can
use the Intelligent Updater to install, publish, and update your .NET Windows
Form-deployed PowerBuilder applications easily.
The .NET Smart Client
Arguably, the biggest headache for application development has
been...deployment. The initial and ongoing appeal of browser-based