View the PowerPoint Slides for this webcast
Upcoming SlideShare
Loading in...5

Like this? Share it with your network


View the PowerPoint Slides for this webcast






Total Views
Views on SlideShare
Embed Views



0 Embeds 0

No embeds



Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
Post Comment
Edit your comment

View the PowerPoint Slides for this webcast Presentation Transcript

  • 1. PowerBuilder 11.2 Feature Overview John Strano Technology Evangelist Sybase, Inc. [email_address]
  • 2. Agenda
    • PowerBuilder Roadmap
    • PowerBuilder 11.2 Feature Overview
    • Demonstration
  • 3. PowerBuilder Roadmap
    • Version 11 released in June 2007
    • 11.1 Maintenance Release in November 2007
    • Delivers on third-phase of PowerBuilder’s .NET initiative
  • 4. Language Independence Application Connectivity Multiple Platform Support Power And Performance 2009 PowerBuilder 12
    • .NET in IDE
    • WPF support at design- and run-time
    • Fully managed code at deployment
    • PowerScript Language Enhancements
    2008 PowerBuilder 11.2
    • AJAX support for Web Forms Applications
    • EAServer .NET Client Support
    • Enhancement requests
    2008 PowerBuilder 11.5
    • Core .NET enhancements
    • DataWindow enhancements for Win32 and .NET
    • Updated database support
    • Enhancement requests
  • 5. PowerBuilder 11.2 Defining Features
    • Certificate Store Support for Smart Client-published Applications
    • Usability and UI Enhancements
    • Database Connectivity Enhancements
    • Enabling the DEBUG Condition for ORCA and OrcaScript
    • Application Pools for Web Forms in IIS7
    • Telerik RadControls Support
    • EAServer Support for .NET-deployed PowerBuilder Clients
    • AJAX Functionality for WebForm-Deployed Applications
  • 6. Certificate Store Support for Smart Client-published Applications
    • As of PowerBuilder 11.0 you can publish your WinForm-deployed application using .NET Smart Client techniques.
    • To be compatible with the .NET security model, applications must be able to be signed with a digital certificate.
    • In PowerBuilder versions 11.0 and 11.1, the developer was required to browse for a certificate file .
  • 7. Certificate Store Support for Smart Client-published Applications
    • Using PowerBuilder 11.2, developers may now additionally browse a digital certificate store in order to securely sign their applications.
    • See Trusted Application Deployment Overview
  • 8. Certificate Store Support for Smart Client-published Applications
  • 9. Usability and User Interface Enhancements
  • 10. Usability and UI Enhancements
    • Target-relative paths and shared projects
      • The developer may need to move a target to a different location in the file system.
      • The developer may want to give a copy of the target to another developer.
  • 11. Usability and UI Enhancements
    • Target-relative paths and shared projects
      • The paths stored in a project object are now adjusted relative to the new target location.
    • Developer A gives a target to Developer B:
      • C: arget1 arget1.pbt
      • C: arget1pblspbl_1.pbl
      • C: arget1pblspbl_2.pbl
      • C: arget1 es arget1.pbr
      • C: arget1out arget1.exe
  • 12. Usability and UI Enhancements
    • When Developer B copies the target to the new directory, no 'manual' changes to paths in the project object are necessary:
      • D:PBMy TargetsTarget 1 arget1.pbt
      • D:PBMy TargetsTarget 1pblspbl_1.pbl
      • D:PBMy TargetsTarget 1pblspbl_2.pbl
      • D:PBMy TargetsTarget 1 es arget1.pbr
      • D:PBMy TargetsTarget 1out arget1.exe
  • 13. Usability and UI Enhancements
    • Library list and .NET Assemblies context menu items on targets in the System Tree
      • The popup menu for Targets in the System Tree has new menu items
        • Library List
        • .NET Assemblies
      • These new menu items will open the Target’s properties response window with the appropriate tab page already selected
  • 14. Usability and UI Enhancements
    • Publish context menu item on Smart Client projects in the System Tree
      • The popup menu for Windows Forms Projects has a new Publish menu item
      • This operation can now be initiated from the System Tree without opening the Project Painter
  • 15. Usability and UI Enhancements
    • Files opened in the File editor are added to the most recently used objects list
  • 16. Usability and UI Enhancements
    • File editor Open dialog box lists additional file types
      • JavaScript
      • HTML
  • 17. Usability and UI Enhancements
    • Current DBMS connection displays in the PowerBuilder title bar
  • 18. Usability and UI Enhancements
    • UseEllipsis property is now available in edit styles in the Database painter
      • UseEllipses was added as a DataWindow property in PowerBuilder 11.0
      • UseEllipses is now available in the Database Painter for Extended Attribute definition
  • 19. Database Connectivity Enhancements
  • 20. Database Connectivity Enhancements
    • The DisableBind DBParm is now supported by the ASE and SYC database interfaces
  • 21. Database Connectivity Enhancements
    • Support for Oracle 10.2 NCHAR literal replacement
      • String literals are converted from the client’s character set to the server’s character set when SQL statements are executed
      • Data in string literals can be lost in this character set conversion
      • NCharLiteral database parameter is to “Yes”
      • An internal character set is used on the client
      • The character set is converted to Unicode on the server to avoid data loss
  • 22. Enabling the DEBUG Condition for ORCA and OrcaScript
    • Conditional Compilation was introduced in PowerBuilder 11.0
      • Enables the developer to maintain one code line for multiple deployment environments
  • 23. Enabling the DEBUG Condition for ORCA and OrcaScript
    • Project objects are currently where you set the inclusion or exclusion of the DEBUG condition when compiling from the IDE.
  • 24. Enabling the DEBUG Condition for ORCA and OrcaScript
    • However, the ORCA tool and OrcaScript commands do not use Project objects to compile applications of standard (Win32) client-server PowerBuilder targets
  • 25. Enabling the DEBUG Condition for ORCA and OrcaScript
    • PowerBuilder 11.2 includes a new OrcaScript property and method that allow you to programmatically compile Win32 PowerBuilder applications using or excluding script contained in conditional compilation blocks set with the DEBUG preprocessor symbol.
    start session set debug false set liblist "testdebuguildapp.pbl" set application "testdebuguildapp.pbl" "testdebug" build application full build executable "destination_1uildapp_p.exe" "iconicon9.ico" "" "N" end session
  • 26. Application Pools for Web Forms in IIS7
    • If you’re using Vista, your deployment target is by default IIS7.
    • Virtual directories for Web applications in IIS 7 are hosted in an application pool .
    • This is the host process for one or more ASP.NET applications.
  • 27. Application Pools for Web Forms in IIS7
    • PowerBuilder deploys WebForm applications to a pool named PBAppPool which uses integrated managed pipeline mode by default.
    • To avoid compatibility issues if your applications use TreeView controls, StaticHyperLink controls, or currency mask conversions, you must designate that PBAppPool use the classic managed pipeline mode .
  • 28. Application Pools for Web Forms in IIS7
  • 29. Telerik RadControls Support
    • As of version 11.2, WebForm-deployed PowerBuilder applications use Telerik RadControls for certain controls by default.
    • Enhanced functionality for :
      • Toolbars and Menus
      • DatePicker and MonthCalendar controls
      • TreeView controls.
  • 30. EAServer Support for .NET-deployed PowerBuilder Clients
    • With PowerBuilder 11.2, your .NET-deployed PowerBuilder Targets can access EAServer
      • Windows Forms
      • Web Forms
      • Assemblies
      • Web Services
    • Through the .NET client ORB, this gives you access to EAServer 6.1-hosted components
      • PowerBuilder NVOs
      • EJBs
  • 31. AJAX for Web Form-Deployed Applications
    • As of PowerBuilder 11.2, Asynchronous JavaScript and XML (AJAX) functionality has been added for WebForm-deployed Targets
    • The performance of WebForm applications has been enhanced by enabling ASP .NET pages to be updated one region at a time
    • This avoids refreshing the entire page for each operation
      • Reduces the volume of data transmitted in network roundtrips
      • Reduces the impact on browser rendering
  • 32. AJAX for Web Form-Deployed Applications
    • Transparent to the PowerBuilder Developer
      • No changes to your application are required
    • ASP.NET AJAX extensions v1.0 must be installed on IIS
      • Install on both development and deployment machines
  • 33. AJAX for Web Form-Deployed Applications
    • Don’t forget to clear cached temporary files from PowerBuilder versions previous to 11.2
      • Output subdirectories in your workspace's directory
      • <server drive>Inetpubwwwroot<your virtual directory>
      • <server drive>Inetpubwwwroot<your virtual directory>_root
      • <server drive>WINDOWSMicrosoft.NETFrameworkv2.0.50727Temporary ASP.NET Files<your application>
  • 34. AJAX for Web Form-Deployed Applications
    • AJAX WebForm Global Properties. The Developer…
      • Can influence the “Waiting MessageBox” properties
      • Can influence how and when menuitem Selected events are executed
      • Disable the status message by setting the PBAjaxWaitingMessage value to an empty string (&quot;&quot;).
  • 35. PowerBuilder 11.2 Demonstration
  • 36. Q&A
  • 37. FAQs
    • Q: I really don’t have to change my application to take advantage of AJAX?
    • A: Correct. However, all ASP.NET-deployed Targets deployed from previous PowerBuilder versions must be fully cleared and redeployed. Please refer to the documentation.
  • 38. FAQs
    • Q: Are there any benchmarks from engineering on the level of performance improvement with AJAX utilization?
    • A: QA did benchmark testing, the results depended on the test scenarios, e.g., the ratio of updated area over the whole page, and the server load etc. In some cases we see 5% improvement, some (DataWindow-intensive report windows) had 50% improvement.
  • 39. FAQs
    • Q: Does AJAX usage mean it's less likely we need to use custom JavaScript?
    • A: Both custom JavaScript and AJAX can enhance performance. Custom JavaScript enhances performance by making modifications without a round trip to the server. AJAX enhances performance by reducing the amount of data in postbacks to the server.
    • Q: Does it impact what we may already have in custom JavaScript?
    • A: There is no impact.
  • 40. FAQs
    • Q: Is there any control over AJAX functionality that a developer has?
    • A: The developer may choose to disable the AJAX functionality by setting the global property PBPostbackType to a value of Synchronous . ( This is a temporary measure for performance comparison and will be removed in a later version.)
  • 41. Q&A
  • 42. Thank you.