Overview: Sybase industry leading application development tools with .NET interoperability.
August 8, 2002 - Sybase announced the initial strategy of PowerBuilder and Microsoft Net architecture interoperability. · Sybase plans to use a four-stage deployment scenario to make PowerBuilder components and applications to implement interoperability with components used in Microsoft.NET. • Developers who use .NET developers can also get high productivity in the application of the extensive Sybase® PowerBuilder® integrated development environment. · Sybase can provide customers with an open product environment, which is conducive to the company to reduce the total cost of operation.
Sybase (New York Stock Exchange Code: SY), a leading enterprise infrastructure and integrated company, recently announced the strategy of PowerBuilder support Microsoft.NET architecture. Sybase leads in the industry's leading fourth-generation Fast Application Development Language (RAD) Tool PowerBuilder will continue to provide development environments to create task-critical, strategic and high productivity applications.
"Today, the meaning of openness is more extensive. For example, communication capabilities of various applications and information processing systems with (in various languages), in any case, and provide operations for users The ability of various applications, "SHJ Nathan, senior vice president and general manager of Sybase Enterprise Solutions, said" Openness also means to support various development environments in the enterprise - including J2EE and .NET platforms. "
Sybase plans to adopt a four-stage solution to implement the interoperability of PowerBuilder components and applications with applications in the Microsoft.NET architecture. The first phase of the PowerBuilder.Net Strategy will adopt the form of supporting Web services, including XML business enhancements to PowerBuilder 9.0.
The second phase will include DataWindow.Net and DataStore.Net features. Using PowerBuilder's exclusive patents in data access, DataWindow.net, and DataStore.Net can support access from non-PowerBuilder applications and can be used by any .NET language.
Experienced PowerBuilder developers If you use .NET, you don't need to learn new lengthy, complex methods to integrate with DataWindow and DataStore.
In the third phase, the Unconventional Objects (NVO) of the package business logic will be migrated to the .NET structure, enabling the PowerBuilder developer to reasonably utilize the current code and move it to the .NET environment. Developers can also achieve high productivity in a similar PowerBuilder integrated development environment (IDE). They can also continue to create applications, develop components in PowerBuilder, and to deploy these applications and components into the business platform and environment.
The final phase of PowerBuilder's .NET support includes bringing components in the .NET architecture into the PowerBuilder IDE. This stage will change the appearance of the PowerBuilder itself so that it looks like the user interface created in .NET. It also allows developers to call .NET system components to create .NET-based objects in PowerBuilder.
With PowerBuilder, app developers can choose the development platform and environment they need, including Windows DNA, .NET architecture, web, and J2EE platforms. It will continue to simplify software development structures, protocols, and standard complexity, enabling developers to focus on writing software applications to solve complex business needs. For new standards and development trends, PowerBuilder developers can make a response according to the direction of the company's choice, add value to existing products.
