The release-defining feature of PowerBuilder 11 is its ability to deploy
existing applications as .NET Windows Forms and Web Forms applications and
components of business logic, namely custom-class user objects (NVOs), as
.NET assemblies and Web Services. Although PowerBuilder's adoption of the
.NET Framework represents a great leap forward for application developers,
the implications of converting a desktop, client/server application to an
ASP.NET Web application are significant. Those of you who have been working
with PowerBuilder 11 know this first hand just from the sometimes daunting
list of unsupported features that can appear in the Output window after
deploying a .NET target (Figure 1).
The unsupported features list contains valuable information necessary for you... (more)
Introduced in 1991 and patented in October 1996, PowerBuilder's DataWindow
technology remains one of the most flexible, dynamic, and versatile means for
data retrieval, modification, and presentation available in any development
tool. By launching DataWindow.NET along with PowerBuilder 10 later this year,
Sybase is continuing its commitment to the four-phased .NET strategy
announced in 2... (more)
Have you ever thought of adding new features to PowerBuilder? Or wanted to
call Java or .NET from PowerScript? Or imagined that you can call PowerScript
from C++ or Java? With PBNI, you can do them all and more. PowerBuilder
Native Interface (PBNI) is a standard interface for third parties to extend
the functionality of PowerBuilder.
PBNI is a valuable new addition to the PowerBuilder pro... (more)
Designing and implementing an n-tier or Internet application is a complex
task, and issues resulting from errors in the runtime configuration or the
application code itself are practically inevitable. Problem analysis and
troubleshooting are part art, part science. Therefore, although the
techniques discussed here can be helpful, the sheer diversity of client and
server environments prec... (more)
Designing and implementing an n-tier or Internet application is a complex
task, and issues resulting from errors in the runtime configuration or in the
application code are practically inevitable. Problem analysis and
troubleshooting are part art and part science. Therefore, although the
techniques we'll discuss are often helpful, the sheer diversity of client and
server environments pre... (more)
Jim O'Neil is a Microsoft Developer Evangelist for the Northeast U.S. where he concentrates on the developer communities using Visual Studio .NET and the various .NET technologies. Prior to joining Microsoft, he was a Principal Systems Consultant and Principal Technical Support Engineer for Sybase, Inc., where he specialized in the PowerBuilder family of tools, EAServer, and Appeon for PowerBuilder.
Manas Sarkar
Lavenya Dilip
Lynn O'Shaughnessy
Crystal Nichols
Saurabh Verma
