Sybase PB12.NET英文版特性指南

需积分: 48 34 浏览量更新于2024-07-27 收藏 1.02MB PDF 举报

"Sybase PB12.NET英文版产品介绍" Sybase PB12.NET是Sybase公司推出的一款集成开发环境（IDE），专为构建企业级.NET应用而设计。这款产品结合了PowerBuilder的强大功能和微软.NET框架的灵活性，提供了一个高效、直观的工具集，用于开发、测试和部署Windows桌面和Web应用程序。主要特点： 1. **.NET集成**：PB12.NET允许开发者使用.NET Framework进行编程，支持C#和VB.NET语言，同时保留了PowerBuilder的PBL（PowerBuilder库）和DataWindow对象，便于现有PowerBuilder项目迁移至.NET平台。 2. **数据窗口增强**：DataWindow作为PowerBuilder的核心组件，在PB12.NET中得到进一步强化，支持更多的数据库连接选项，包括ADO.NET，以及更复杂的数据操作和展示功能。 3. **Web应用开发**：除了传统的桌面应用，PB12.NET还支持创建Web应用程序，通过WebWindow和WebService功能，可以无缝地将PowerBuilder应用扩展到Web环境中。 4. **现代UI设计**：提供了全新的用户界面设计工具，支持WPF（Windows Presentation Foundation）和Windows Forms，使得应用界面更加现代且响应式。 5. **版本控制集成**：集成版本控制系统如Visual SourceSafe或Subversion，帮助团队协作和管理源代码。 6. **调试和性能优化**：强大的调试工具集，包括对本地和远程应用的调试支持，以及性能分析器，帮助开发者识别和解决性能瓶颈。 7. **国际化和本地化**：支持多语言环境，方便应用的全球化部署，同时提供了丰富的本地化工具，简化了语言包的创建。 8. **API和第三方库集成**：允许开发者利用.NET Framework中的大量类库和API，同时支持与第三方控件和组件的集成。 9. **代码自动生成**：自动代码生成功能，减少了手动编写重复代码的工作量，提高了开发效率。 10. **持续集成与部署**：支持自动化构建和部署流程，简化了软件生命周期管理。总结来说，Sybase PB12.NET是针对.NET开发者的强大工具，它结合了PowerBuilder的传统优势和.NET的现代特性，旨在提升开发效率，简化企业级应用的构建过程。对于已有的PowerBuilder开发者，PB12.NET提供了一个平滑的过渡路径，让他们能够在.NET平台上继续发挥其技能。同时，对于.NET开发者来说，PB12.NET引入了独特的PowerBuilder功能，扩展了他们的开发选择。

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页未读，继续阅读

kokoyou

粉丝: 0
资源: 6

Sybase PB12.NET英文版特性指南

利用PB.net创建WPF应用教程第1部分

Sybase ADO.NET2 驱动

Sybase 12.5 ADO.NET 客户端DLL

asp.net Sybase乱码

doris sybase

sybase sql anywheren7

在Windows 64位系统中安装Sybase ODBC驱动的详细步骤是什么，以便建立与Sybase数据库的连接？

如何在Windows 64位系统上安装Sybase ODBC驱动，并配置连接至Sybase数据库的步骤？

SYBASE for linux

在Sybase数据库安装完毕后，如何通过SqlDbx工具连接到特定的Sybase服务器并配置正确的字符集以确保数据无乱码？

最新资源