Sybase PowerBuilder.NET 12 教程：功能指南

4星 · 超过85%的资源需积分: 48 177 浏览量更新于2024-07-31 6 收藏 1.02MB PDF 举报

"Sybase PowerBuilder.NET 12 教程" Sybase PowerBuilder.NET 12 是一个强大的、面向对象的开发工具，专为构建企业级的.NET应用程序而设计。这款教程涵盖了该版本的主要特性、功能和使用方法，旨在帮助开发者高效地利用PowerBuilder.NET 12创建和维护高质量的应用程序。 1. **PowerBuilder.NET概述** - PowerBuilder.NET 12 是基于PowerBuilder的经典版本，但与.NET框架集成，提供了对.NET Framework的全面支持。 - 它提供了一个拖放式的开发环境，简化了用户界面设计和业务逻辑的实现。 2. **.NET集成** - PowerBuilder.NET 12 支持.NET Framework的类库，允许开发者使用C#、VB.NET等.NET语言编写的组件。 - 它提供了PBL到DLL的转换，使得.NET Framework中的类库可以直接在PowerBuilder项目中使用。 3. **数据窗口技术** - 数据窗口是PowerBuilder的核心组件，用于处理数据库操作。在PowerBuilder.NET 12中，数据窗口继续强化，支持更多的SQL语句和数据源，以及更灵活的数据展示和操作方式。 4. **Web应用程序开发** - PowerBuilder.NET 12 引入了Web窗体和Web服务的开发支持，开发者可以创建ASP.NET应用程序和Web服务，扩展了PowerBuilder的网络应用能力。 5. **对象模型和编程接口** - PowerScript，PowerBuilder的内置脚本语言，得到了更新，以适应.NET的编程模式。它提供了与.NET Framework的无缝对接，增强了类型安全性和面向对象的特性。 - 开发者可以通过.NET API扩展PowerBuilder的功能，或与其他.NET应用程序交互。 6. **调试和测试工具** - 提供了完善的调试器，支持断点、单步执行、变量查看等功能，帮助开发者找出并修复代码中的问题。 - 集成了性能分析工具，有助于优化应用程序的性能。 7. **版本控制集成** - PowerBuilder.NET 12 支持多种版本控制系统，如Visual SourceSafe、CVS等，方便团队协作开发。 8. **国际化和本地化** - 支持多语言环境，使应用程序能够轻松适应不同地区的需求。 9. **文档和学习资源** - 提供详细的文档，包括特性和功能指南，帮助开发者快速上手和深入学习。 - 官方可能提供技术支持、社区论坛和在线资源，以解决开发过程中的问题。 10. **许可证协议** - 软件使用受许可证协议限制，必须按照协议条款使用或复制软件。 Sybase PowerBuilder.NET 12 教程为开发者提供了一套全面的学习路径，涵盖了从基础概念到高级特性的所有内容，是掌握PowerBuilder.NET 12开发技能的关键资源。通过这个教程，开发者可以充分利用PowerBuilder.NET 12的特性，构建出高效、稳定且易于维护的企业级.NET应用程序。

What is PowerBuilder .NET

Graphic User Interface

Although PowerBuilder .NET and PowerBuilder Classic share many GUI elements, there are also a number of

differences. Many of the differences are the result of the isolated Visual Studio shell that is integrated into PowerBuilder .NET.

The features in the following table are supplied with the Microsoft Visual Studio shell. You can use the F1 key from a

Visual Studio shell feature to open the H2 Help, and in Visual Studio shell dialog boxes you can click the question mark

icon in the title bar for the H2 Help. The Help for these features is also supplied by Microsoft.

Visual Studio shell feature Comment

XAML editor The eXtensible Application Markup Language (XAML) allows you to code the presen-

tation aspects of your applications separate from the business logic that you code in the

PowerBuilder .NET painter Script views. Changes that you make in the painter designer

views are reflected in the XAML editor code, and changes you make in the XAML editor

can be seen in the designer views. You can only view the XAML editor for a painter when

the Layout view is also visible.

Object Browser The Object Browser allows you to view all .NET Framework classes. It is accessible from

the View menu and is separate from the classic PowerBuilder Object Browser that is also

available from the View menu.

Source control Source control functionality is available from the File>Source Control menu of Power-

Builder .NET. PBG files are no longer required, because exported objects are not com-

piled into a binary PBL file as in PowerBuilder Classic. The Visual Studio shell source

control functionality also does not use PBC files.

Code Snippets Manager The Code Snippets Manager replaces the PowerBuilder Classic Clip window, and allows

you to add XML snippets as well as PowerScript snippets. You can insert snippets from

the pop-up menu in painter Script views. The Code Snippet Manager is available from the

Tools menu.

Command window You open the Command window from the View>Other Windows menu. It allows you to

execute commands from the design time environment. Intellisense is active in the Com-

mand window to assist you in scripting valid commands for your targets.

Document outline The Document Outline view enables you to see a list of controls available in the current

painter. It replaces the Control List and Non-Visual Object List in PowerBuilder Classic,

but it also shows the control hierarchy. You can open the Document Outline view from the

View>Other Windows cascading menu.

Toolbox Replaces the tool selection facility in the painter toolbars and Insert menu in Power-

Builder Classic. You open the toolbox from the PowerBuilder .NET View menu. You can

add or remove toolbox items from the Tools>Choose Toolbox Items menu.

Intellisense Replaces PowerBuilder Classic autoscript, but also provides selections for classes, meth-

ods, and members of all assemblies included in target references. Intellisense is available

in painter Script views, in the XAML editor, from the Edit menu, and in the Command

window.

Properties window The Properties window replaces the Properties view in PowerBuilder Classic painters. It

allows you to sort properties by category or alphabetically, and when opened from the

View>Properties Window menu, has a status line to describe a selected property.

Configuration You open the Configruration Manager from the Properties pages dialog box for each

PowerBuilder .NET workspace/solution. Release and Debug configurations are provided

by default, although you can add and edit configurations from the Configuration Manager.

You can change the deployment platform for a particular configuration, and you can open

the Edit Project Configurations dialog box from the Configuration Manager to rename or

remove a configuration that you added.

Graphic User Interface

PowerBuilder .NET Features Guide 9

Visual Studio shell feature Comment

Bookmark window You can enable and toggle bookmarks in painter Script views or in the XAML editor from

the Edit>Bookmarks cascading menu. You open the Bookmark window from the

View>Other Windows cascading menu.

Find and Replace The PowerBuilder .NET Find and Replace dialog box has tabs for Quick Find and Quick

Replace. It is available from the Edit>Find and Replace menu, and it allows you to

bookmark all items that match the Find string.

Layout view The painter Layout views use the Visual Studio designer and are closely associated with

the XAML editor. A magnifier bar in the upper left corner of each Layout view allows you

to change the magnification of objects and controls at design time without changing their

size at runtime. The close (x) icon at top right corner closes only the current tab of the

painter. If you click this icon while the Layout view is current, the Layout tab closes and

the Script (code-behind) view becomes current.

File editor The Open With dialog box replaces the File Editor in PowerBuilder Classic. It allows you

to select an editor for text in the Script views or XAML editor, or for current items in the

System Tree. It also allows you to add editors that you want to use to view these files, and

set a different editor as the default file viewing selection. You can open this dialog box

from the View>Open With menu item.

Text formatting In PowerBuilder .NET, you can format text in painter Script views, in the XAML editor,

and in the Command window with the Edit>Advanced cascading menu items.

Task list Replaces the PowerBuilder Classic To-Do List. You can open the Task list by selecting the

View>Other Windows>Task List menu item.

System Tree in PowerBuilder .NET

The System Tree in PowerBuilder .NET functions in many ways like the System Tree in PowerBuilder Classic, although

for some functionality it appears more like the Solution Explorer in Microsoft Visual Studio.

The System Tree is typically the central point of action in PowerBuilder programming. It provides access to all the objects

in a PowerBuilder workspace.

The System Tree inPowerBuilder Classic displays objects in PowerBuilder libraries (PBLs), whereas in

PowerBuilder .NET, the PBLs have been converted to directories, and the System Tree displays the contents of the PBL

directories only as separate files. The implementation of the PowerBuilder .NET System Tree as a Solution Explorer

extension has or enables several enhancements:

• Integration with the Solution Explorer "Find" subsystem

• Provision of a more natural framework for opening editors

• Replacement of an ad-hoc framework for source control

• Provision of a more natural framework for workspace and project persistence

• Enabling extensions for things like code refactoring

• Ability to drag and drop files from the Windows Explorer to targets and libraries

• Listing of all assemblies used by a target in a single References folder

• Ability to select a set of nodes to perform a common action, such as applying a comment or changing a common

writeable property

• Ability to host targets with multiple application objects and to set one of those objects as the current application

object.

However, there is also System Tree functionality that is no longer available with the file orientation of the

PowerBuilder .NET System Tree. This includes:

• Dragging and dropping objects to the PowerScript editor or painters

• Using the System Tree to navigate directly to nested controls or specific methods and properties

Graphic User Interface

• Displaying of the source control status of objects in the System Tree

Some functionality operates similarly in the PowerBuilder Classic System Tree and in the PowerBuilder .NET System

Tree. Double-clicking an item in the System Tree executes the default action for that item. Right-clicking an item opens

the pop-up menu for that item.

The following pop-up menu items on a PowerBuilder Classic System Tree object are not available in the System Tree in

PowerBuilder .NET:

• PBNI Extensions

PowerBuilder .NET library nodes do not have the Import PowerBuilder Extension pop-up menu item for importing

PBNI extensions.

• Optimize

In PowerBuilder Classic, the Optimize menu item provides a way to clean up deleted objects and items that have been

accumulated in target PBLs. This is not necessary in PowerBuilder .NET.

• Migrate

The PowerBuilder Classic migrate capability assumes you can view a target in the System Tree that does not list

objects in an expanded PBL format. In PowerBuilder .NET, objects are always listed in an expanded format, so the

Migrate pop-up menu item is not necessary.

The other use of the Migrate pop-up menu is to regenerate PCode from the sources for an object, and this is also not

needed in PowerBuilder .NET.

• Separate Library List and .NET Assemblies

Separate pop-up menu items for the library list and .NET assemblies are not needed inPowerBuilder .NETbecause of

their functional equivalence. Instead, a single pop-up menu item, "Library List", lists all PBLs and .NET assemblies

in PowerBuilder .NET targets.

• Regenerate

Like the Optimize and Migrate pop-up menu items, the Regenerate menu item is not needed in the PowerBuilder .NET

System Tree because objects are always listed in an expanded format.

WPF Visual Controls in PowerBuilder

The system defined visual controls that you include in PowerBuilder .NET applications maintain the class hierarchy of

traditional PowerBuilder runtime controls, but the WPF controls are referenced in Extensible Application Markup

Language (XAML) files.

The following table maps PowerBuilder visual controls with their WPF equivalents:

Windows 32 Control WPF Control Equivalent

CommandButton and PictureButton Button

CheckBox CheckBox

DataWindow DataWindow WPF control

DropDownListBox and DropDownPictureListBox ComboBox

EditMask EditMask WPF control

Graph Graph WPF control

GroupBox GroupBox

HProgressBar and VProgressBar ProgressBar

HScrollBar and VScrollBar ScrollBar

HTrackBar and VTrackBar Slider

InkPicture InkCanvas

Graphic User Interface

PowerBuilder .NET Features Guide 11

Windows 32 Control WPF Control Equivalent

ListBox and PictureListBox ListBox

ListView ListView

Menu Menu/Toolbar

MenuCascade Menu

MultilineEdit and SingleLineEdit TextBox

Picture and PictureHyperLink Image

RadioButton RadioButton

RichTextEdit RichTextBox

StaticHyperLink HyperLink

StaticText Label

Tab TabControl

TreeView TreeView

Window Window/Grid

The following visual controls have no current WPF control equivalents: Animation, DateTimePicker, DragObject,

InkEdit, and MonthCalendar.

PowerBuilder .NET Toolbox

The Toolbox displays icons for controls that you can add to applications.

The Toolbox is available from the View menu. You can dock the Toolbox and either leave it pinned open or set it to Auto

Hide.

You can drag and drop an item onto a design surface (such as a window painter) or copy and paste it into a code editor

within PowerBuilder .NET. Either action adds the fundamental code to create an instance of the Toolbox item in the active

project file.

In PowerBuilder .NET, the Toolbar is initially provided with two tabs:

WPF

Workshop

Controls

Preloaded with PowerBuilder .NET-specific controls.

The list of controls depends on the object that has focus. For example, when a Window painter is active,

the controls that can be added to that painter become available in the Toolbar. If you change focus to a

different object, the items available in the Toolbar might change.

General

Initially, the General tab is empty, but you can add items that you want to store for later reuse, including

these kinds:

• Controls

• .NET Framework components

• Your own or third-party components

• Reusable text or code snippets

For example, you can highlight some code in a script window and drag it to the General tab to create a

reusable item. Or, you can copy an EventLog component and paste it in the toolbox. These items are

ready to be dragged from the General tab and dropped into the code editor or onto the active design

surface.

See the Toolbox topics in Visual Studio Help for details about basic Toolbox usage and customization.

Graphic User Interface

剩余169页未读，继续阅读

yugandong2

粉丝: 0
资源: 5

Sybase PowerBuilder.NET 12 教程：功能指南

pb12.5[5629]不限时学习的解决办法亲测可用

SAP Powerbuilder 12.6 （4081）无限时学习破解文件

PB.NET环境配置.docx

powerbuilder9.0安装教程

powerbuilder12下载 csdn

给一些power builder开发的实例教程网址

powerbuilder做webservice教程

powerbuilder安装教程

powerbuilder12.5安装教程

powerbuilder下载教程

最新资源