PowerBuilder .NET 12.0 功能指南（英文版）PDF下载

下载需积分: 10 | PDF格式 | 1.6MB | 更新于2024-07-21 | 114 浏览量 | 举报

PowerBuilder.NET 12.0 是一款基于Sybase技术的集成开发环境（IDE），它将PowerBuilder的传统特性与.NET框架相结合，为应用程序开发者提供了在Windows平台上构建高性能、跨平台应用的能力。该英文版PDF文档，文档ID为DC01261-01-1200-01，最后修订日期为2010年3月，版权归属Sybase， Inc.，并声明所有权利保留。此指南详细介绍了PowerBuilder .NET 12.0 的主要新功能、升级和改进，包括但不限于： 1. **跨平台支持**：PowerBuilder.NET 12.0 支持.NET Framework，使得开发者能够轻松地创建可以在Windows、Mac和Linux等操作系统上运行的应用程序，提升了应用的兼容性和市场适应性。 2. **集成.NET库和API**：该版本允许无缝访问.NET框架中的类库和组件，如ASP.NET、ADO.NET和WCF，这极大扩展了应用的功能和性能，增强了与Windows生态系统的交互能力。 3. **面向对象编程强化**：PowerBuilder.NET 12.0 提供了更丰富的面向对象工具，包括重构支持和更好的代码组织结构，有助于提高代码质量和开发效率。 4. **Web服务集成**：文档可能涵盖了如何利用PowerBuilder构建和调用SOAP和RESTful Web服务，以及处理XML数据的能力。 5. **图形用户界面（GUI）设计**：新版可能引入了改进的控件库和布局工具，使得创建现代化UI更为直观和高效。 6. **性能优化**：通过底层优化，PowerBuilder.NET 12.0 可能提供了更快的数据处理速度和内存管理，确保应用在高并发环境下的稳定运行。 7. **安全性增强**：文档可能会涉及如何集成.NET的安全模型，如身份验证、授权和加密，以保护敏感数据。 8. **文档和教程**：该文档不仅包含了技术细节，还可能包含学习资源、示例代码和最佳实践，以帮助用户快速上手和深入理解PowerBuilder.NET。 9. **升级和维护**：由于是升级指南，它会指导用户如何从旧版本平滑过渡到12.0，并处理可能出现的迁移问题。 10. **法律条款**：文档中重申了软件许可协议，强调未经Sybase书面许可，用户不能复制、传播或翻译任何部分内容，体现了对知识产权的尊重。 PowerBuilder.NET 12.0 Features Guide 是一本实用的参考手册，对于希望通过PowerBuilder开发.NET应用程序的专业人士来说，是必不可少的学习和参考资源。通过深入理解和掌握其中的特性，开发者可以更好地利用PowerBuilder的强大功能，提升项目的质量和竞争力。

independent technologies and blend them together without much built-in support. WPF

applications allow you to use all these features with a consistent programming model.

• Resolution independence – WPF lets you shrink or enlarge elements on the screen,

independent of the screen’s resolution. It uses vector graphics to make your applications

resolution-independent.

• Hardware acceleration – WPF is built on top of Direct3D, which offloads work to graphics

processing units (GPUs) instead of central processor units (CPUs). This provides WPF

applications with the benefit of hardware acceleration, permitting smoother graphics and

enhanced performance.

• Declarative programming – WPF uses Extensible Application Markup Language

(XAML) declarative programming to define the layout of application objects and to

represent 3-D models, among other things. This allows graphic designers to directly

contribute to the look and feel of WPF applications.

• Rich composition and customization – WPF controls are easily customizable. You need

not write any code to customize controls in very unique ways. WPF also lets you create

skins for applications that have radically different looks.

• Easy deployment – WPF provides options for deploying traditional Windows applications

(using Windows Installer or ClickOnce) . This feature is not unique to WPF, but is still an

important component of the technology.

• Culturally aware controls – static text in controls and the return data for the String function

are modified according to the culture and language specified by the end user's operating

system.

WPF is also more suitable for applications with rich media content than Windows Forms

applications. This includes applications using:

• Multimedia and animation with DirectX technology

• HD video playback

• XPS documentation for high quality printing

• Control rotation (Windows Forms applications support text rotation only)

Modified and Unsupported Features in PowerBuilder .NET

Some features in PowerBuilder Classic are not supported in PowerBuilder .NET. Other

features are partially supported or use a different method to obtain similar results or to display

similar functionality.

Several differences are the result of .NET restrictions, or the Visual Studio isolated shell

designer and functionality that PowerBuilder .NET leverages. The following features are not

currently supported or are only partially supported in PowerBuilder .NET:

• Target location – you can save workspaces and libraries to the root directories of computer

drives, but do not save PowerBuilder .NET target files (PBTX) to root directories.

About PowerBuilder .NET

6 PowerBuilder .NET

• Event sequence – the difference in event sequence in WPF applications may affect

applications that are dependent on a strict order of triggered events. You must manually

refactor migrated applications to take into account the order of triggered events.

Although Web Forms applications also use a different event sequence than Windows 32 or

Windows Forms applications, in Web Forms applications, you can save the events to a

queue and execute them during a postback operation. For WPF applications, events must

be handled immediately after they fire.

• User-defined custom events (partial support) – PowerBuilder .NET uses a different event

model than PowerBuilder Classic. For a list of supported custom events in

PowerBuilder .NET, see

Supported Custom Events

• Fonts that are not TrueType or OpenType fonts – although you can only select installed

TrueType or OpenType fonts in PowerBuilder .NET, you can still enter the names of other

fonts for the FaceName property of controls that display text. You can also migrate

applications that use non-TrueType fonts from PowerBuilder Classic. However, at

runtime, the .NET Framework replaces fonts that are not TrueType or OpenType fonts,

causing unexpected changes to the way the text appears to end users of

PowerBuilder .NET applications.

• Coding restrictions – several PowerScript coding practices, such as dashes in identifiers or

colons for microsecond separators in time functions, are not permitted in .NET

environments. For more information, see

Coding Restrictions

• Section 508 support – uses UI Automation (UIA) to implement accessibility instead of the

Microsoft Active Accessibility (MSAA) used by PowerBuilder Classic. UIA implements

a UIA-to-MSAA bridge, so you can still use MSAA tools for application accessibility in

PowerBuilder .NET. You can also use newer tools based on UIA for this purpose.

UIA supports the AccessibleName property, but does not support the AccessibleRole and

AccessibleDescription properties on windows and controls that inherit from DragObject.

• Window previews – do not work for untitled windows. You must save a window before you

can preview it at design time.

• Control handles – in PowerBuilder Classic applications, each control has its own window

handle, and many operations depend on the window handle. In PowerBuilder .NET, there

is only a single "big" handle for a window, but the controls nested in a window do not have

their own handles. You must refactor migrated applications that use API calls relying on

control handles before importing them to PowerBuilder .NET.

• Design-time list views – the Control List, Non-Visual Object List, Function List, and

Event List views are replaced in PowerBuilder .NET by the Document Outline and the PB

Object Outline.

• Library painter and the (PowerScript) Browser – most of the functionality of the Library

painter and the Browser is available from Solution Explorer context menu items and the

PB Object Outline.

• External visual objects – are not supported in PowerBuilder .NET. You must remove these

objects manually before you migrate applications from PowerBuilder Classic. Although

the Migration wizard reports unsupported system features, it does not report user-defined

features, such as external visual objects, that are unsupported.

About PowerBuilder .NET

Features Guide 7

• Resource files – are added directly to a target or a folder under the target.

PowerBuilder .NET does not use PBR files, although if you convert a target from

PowerBuilder Classic, the new target wizard lets you select resources that are listed in a

PBR file associated with the target you are converting.

• The Plug-in Manager – in the PowerBuilder Classic IDE is replaced in

PowerBuilder .NET by the Add-in Manager from the Visual Studio isolated shell. To

enable add-ins, see

Add-ins in the PowerBuilder .NET Environment

• Pipeline and query objects – cannot be created from the New dialog box. In

PowerBuilder .NET, you can create query objects only in the SQL Dialog invoked from the

DataWindow painter, although you can also import or migrate them from PowerBuilder

Classic. Pipeline objects are not currently supported in PowerBuilder .NET, and if you

import or migrate these objects, they are ignored at runtime.

• OLE controls – only partially supported in PowerBuilder .NET.

• PBNI (including PBDOM objects) – are not supported in PowerBuilder .NET.

• Profile- and trace-related objects – are not supported in PowerBuilder .NET.

• EAServer components – are not supported in PowerBuilder .NET.

• EMF and WMF image formats – these formats are not supported by WPF because they are

more susceptible to security vulnerabilities than other image formats.

• Syntax checking – occurs in the background, and you do not need to save or compile a

script to detect any scripting errors, or force the parser to check for errors by selecting the

Edit > CheckSyntax menu item. The Script Editor inserts a red caret under the errors that

it detects, and you can also view the list of detected errors in the Error List window.

However, semantic error checking in PowerBuilder .NET is currently not as robust as in

PowerBuilder Classic.

• Passing strings by reference – before passing a string to an external function by reference

in PowerBuilder .NET, allocate memory for the string by calling the Space system

function. This enables you to pass the same string to the function in subsequent calls to the

function, even if the string becomes empty.

• Global variables and global external functions – can only be declared in the Application

object of a WPF Window Application target.

•

Timer system function – may require the WindowName parameter to trigger the Timer

event, particularly if several windows are open. This parameter is optional in

PowerBuilder Classic. Also, there is a slight timing interval difference (typically about 1

millisecond) due to the threading model in WPF applications.

• Debugger – is now based on the Visual Studio debugger. The

Debugger Changes

topic

summarizes differences with the PowerBuilder Classic debugger.

• Source control – connections to source control use completely different mechanisms in

PowerBuilder .NET and PowerBuilder Classic. For more information, see

Source Control

in PowerBuilder .NET

• Resource objects – all DataWindow and query objects in WPF targets are compiled in a

separate DLL (

appName

.resource.dll) rather than in the application executable.

About PowerBuilder .NET

8 PowerBuilder .NET

Control property or

functionality

PowerBuilder Classic be‐

havior

PowerBuilder .NET be‐

havior

DatePicker font size You cannot save negative font

sizes at design time, but positive

font sizes are saved as negative

values. If positive values are set

at runtime, the actual text size

for the text box part of the con-

trol is converted from Power-

Builder units to units for a logi-

cal device (such as a screen),

and is relatively smaller than the

actual font size that appears

when you set the same values

preceded by a minus sign. How-

ever, this calculation is not per-

formed for the calendar part of

the control, where text sizes ap-

pear as they would if the set val-

ues were preceded by a minus

sign.

As in PowerBuilder Classic,

you cannot save negative font

sizes at design time, but positve

font sizes can be saved as posi-

tive values if you set these in the

XAML editor. At runtime, Pow-

erBuilder .NET uses the same

calculation for converting posi-

tive values as PowerBuilder

Classic, but the converted val-

ues apply to both the text box

and calendar parts of the con-

trol. For more precise font sizes

that do not depend on unit con-

version, you can set negative

values at runtime.

DatePicker ValueChanged

event

Date entry by user triggers event

automatically.

User must press Enter key or

change focus before the event

can be triggered.

EditMask default mask when

decimal mask is invalid

No default mask. Behavior is

undefined.

EditMask uses ##,###.## as its

default mask.

EditMask empty mask for Date,

Time, and DateTime datatypes

Uses static masks: dd/mm/yyyy,

hh:mm:ss:fff, and dd/mm/yyyy

hh:mm:ss:fff.

Uses masks based on the culture

set for the runtime operating

system.

EditMask with percent sign in

mask string

The percent sign is appended to

any numeric value entered. For

example, for a 0.00% mask, if

you set the Text property to 5,

the resulting value is 5.00%.

The numeric value set for the

Text property is first multiplied

by 100 before the percent sign is

added. For a 0.00% mask, if you

set the Text property to 5, the

resulting value is 500.00%. This

matches the behavior of Data-

Window edit formats that

change calculated decimal val-

ues into percentages.

About PowerBuilder .NET

10 PowerBuilder .NET

剩余239页未读，继续阅读

niehanmin

粉丝: 753
资源: 623

PowerBuilder .NET 12.0 功能指南（英文版）PDF下载

powerbuilder.net 12 教程

PowerBuilder12.0绿色版

PowerBuilder .NET 12.0 功能指南

PowerBuilder .NET Web Form

DW2XLS 4.0 for PowerBuilder v12.0 build 5530

Lines98_99_4r.ketnoitatca.net_.zip_powerbuilder .net

PowerScript语言使用手册：PowerBuilder Classic 12.0

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

PowerBuilder .NET教程：PB12开发指南

PowerBuilder.NET在Linux上的应用探索

最新资源