1. PowerBuilder.NET Guided Tour

2. PowerBuilder A New PowerBuilder IDE for.NET Development

3. PowerBuilder A New PowerBuilder IDE for WPF Development  Leveraging Visual Studio features  Isolated Shell provides framework and features  UI  Editor  WPF Designer  Debugger  Plug-in existing PowerBuilder components  Database Painter  SQL Painter  etc.

4. PowerBuilder A New PowerBuilder IDE for WPF Development  Provides a familiar PowerBuilder experience  Little or no re-training  Provides usability enhancements consistent with other major IDEs  Keeps PowerBuilder current with latest functionality

5. PowerBuilder A New PowerBuilder IDE for WPF Development  PowerScript in the VS Core Editor  WPF Painters  Incl. WPF DataWindow Painter  Tabbed documents  Auto-hide for tool panes  3rd Party Add-ins  Import/Export IDE Settings

6. PowerBuilder A New PowerBuilder IDE for WPF Development…and more… Benefits for…  WPF Application Targets .NET Assembly Targets .NET Web Service Targets

7. PowerBuilder Virtual PowerBuilder Libraries  PBLs are now folders  PowerBuilder classes/objects are now files  PBLs track files  Adding a file to a PBL folder does not by itself add it to the PBL  Simplification of source control  Saving with compilation errors now supported

8. PowerBuilder WPF Painters (Window, Visual UserObject)  WYSIWYG design surface for adding, moving, resizing, positioning of controls  XAML editor for optional advanced editing of layout, contents, and behavior  WYSIWYG Preview (WPF, vector-based)  Support for 3rd party controls

9. PowerBuilder Adding 3 rd Party WPF Controls to the Toolbox  A dialog will be provided to select the 3rd party WPF control to import.  Controls may be added to the Toolbox of the …  Window  UO  DataWindow …painters

10. PowerBuilder New PowerScript Editor Features  Intellisense (including for the DataWindow)  Syntax Highlighting  Bookmarks  Code Outlining (collapsing sections)  Highlight of matching elements  Incremental Search  Line Numbering  Go to definition  Code Snippets  Surround With  Split Screen Editing  Error Markers

11. PowerBuilder Other Painters  Database Painter  Query Painter  Structure Painter  …will essentially have the same UI as in PowerBuilder Classic

12. PowerBuilder Other Painters …cont’d…  Menu Painter  Similar to the PowerBuilder Classic IDE’s Menu Painter  Library Painter  Will be consolidated with the System Tree  A list tool window for “details”  SQL Dialog  Will have the same UI as in DataWindow.NET 2.5…a modal dialog

13. PowerBuilder Exercise One  Build a simple “Hello World” Application  Create a Solution  Create a Target  Create a WPF Window  Create an ODBC Connection to SQL Anywhere  Add code in Application Object to connect to Database  Create a DataWindow  Add DataWindow control to WPF Window  Assign DataWindow Object  Code SetTransObject and Retrieve function calls  Build Application  Run Application

14. PowerBuilder Exercise Two  Migrate an Existing Win32 Application to WPF  Use Wizard to create solution and target  Review Unsupported Features List  Build Target  Run Application  What needs to be fixed?

15. PowerBuilder Exercise Three  Powerscript Language Enhancements  Array Enhancement  Jagged Array Enhancement  Return Array from Function or Event

16. PowerBuilder PowerBuilder “Classic” IDE  Current IDE remains intact for:  Traditional Client/Server targets  Winform/Webform targets  EAServer/PASP components  Microsoft will not be investing in Winforms/Webforms  Currently considering Win32 enhancements for a post PowerBuilder 12.0 release (Windows 7 features support)  Sybase will continue to support current DBMS and operating system platforms with maintenance releases.

17. PowerBuilder Summary: PowerBuilder.NET  Build WPF applications with a familiar PowerBuilder experience  Provide your users with rich, progressive user interfaces

18. PowerBuilder Summary: The PowerBuilder WPF Workshop  No need to go to another tool for your.NET requirements  Extend your skills and your existing code to new incarnations of the.NET framework