Challenge of Day

Tuesday, October 27, 2009

PowerBuilder 12 Beta 2 Presentation by Sybex

Today I watched the live official webcast about PowerBuilder 12 Beta 2 by Sybex company. For a long time developers were waiting about this event to see what is new in PowerBuilder 12.
First interesting point to my eyes is the estimated launch time of this product which will be second quarter 2010 which is almost 8 month from now. It means that whatever was presented today, was just a prototype.
I believe Sybex decided to support .NET platform because it was not successful in its Java targets (Tiger) in previous versions of PowerBuilder. Sybex could not find its place in the community of Java Open Source developers and could not impress the technology with its products and as a result, they decided to return back to Microsoft managed code platform.
Based on the presentation, they have just created a PowerBuilder to C# translator and then they call C# compiler from Visual Studio to generate managed code. I think they would have better just create a compiler for PowerScript.
They do not support compact framework, LINQ, Silverlight and many other new feathers in the framework and based my experience from PowerBuilder, in the same way that previous version was not integrated thightly with Java technology, the new generation will not be integrated with .NET framework.
At the end I have pasted list of question and answeres from technical team. It will help you realize more about this product.

Be a winner in your daily challenges
Ali Khademi

+++++++++++++ Here is the questions and answers from live cast +++++++++++++++++++++++++

Question: Migration of a PFC app to .net is possible now? It was not in beta 1.
Answer: I believe the runtime team has been able to migrate some PFC apps
Question: Can we get a copy of this PowerPoint somehow?
Answer: Yes, please send me your email address at and I will follow up with you
Question: what does wpf stand for
Answer: Windows Presentation Foundation (a TM of Microsoft)
Question: PB code is migrated to .NET. does that mean it will generate C# or other .NET app code? or it will still be a PB code (PB Script)
Answer: THere is an intermediate generation of C#, and that is compiled. You still code in PowerScript and XAML
Question: What is the future of Datawindow.Net?
Answer: We are going to evaluate the product after we deliver PB 12 to market. All of our engineering resources have been reallocated to working on v12 as it is such a significant release.
Question: Will the behavior of PB WPF controls be made more consistent with standard WPF controls? (ie: auto-resizing)
Answer: PB WPF controls are inherited from std WPF controls, and so support the same behavior...the difference you may be seeing is in the set of properties generated for the PB controls. You can change the width and height to "auto" to get auto-resize
Question: Can PB.NET WPF windows be integrated into a standard WPF .NET application (in Visual Studio)?
Answer: I am not sure I understand the question - if you are asking if you can develop parts of an application in PB and parts in VS, the answer is yes. PB builds and deploys .NET code.
Question: Can we open ancestor and child object at the same time? Was not it better that you just supply your PB# compiler instead of your ide?
Private Answer: This was just answered...
Question: will we be able to import datawindow at runtime from syntax stored in database in WPF mode?
Answer: yes
Question: will PB(Power Script) be added as a separat (NEW) language for .NET development? like PB.NET / C# . NET?
Answer: If you're asking if it wil be added to Visual Studio, the are not plans at the current time to do so.
Question: but it will be similar to C#/.NET?
Answer: It will produce managed code like any other .net language and can communicate with any .net language, which is the point of having different languages all run in the CLR. We don't want to change powerbuilder's language because that is what makes developing in PowerBuilder so simple! And, unlike MSOFT or any other vendor, we are protecting our customers' existing investment in code, and not going to make them learn a new language.
Question: Any enhancement to the source control interface? Automated build scripts (pull a PB application from source control by date/label and build it purely from what's in the repository) are currently very difficult. (Using TFS here)
Answer: Our goal is to support what VS has in the shell, including TFS in the future. For now, we still provide support to source code control via the MS SCC interface.
Question: I guess to clarify my question further can you launch PB WPF windows stored in a PB target (assembly) from a master WPF application written in C# easily?
Answer: Unfortunately, this is not a use case we've looked at.
Question: Books availalbe for PB 11.5 or PB 12????
Answer: There are lots of online tutorials and samples being created for learning these releases.
Question: When the pocket powerbuilder with CE .NET framework is available?
Answer: We currently don't have a schedule for delivering this support. Like with DW .NET, we are waiting until we are ready to deliver v12, and will then re-evaluate the product roadmap at that time. Part of the challenge is waiting to see what MSOFT delivers for Windows Mobile 7. Ultimately, we want mobile targets inside of PowerBuilder and customers should be able to leverage existing PocketBuilder code and bring it back inside of PowerBuilder
Question: You have not looked at it from the standpoint of trying it or it will not work? We have a lot of legacy PB code and new C# .NET WPF code. We are looking to migrate our PB Classic code to PB.NET and I am wondering if it is possible?
Answer: I may have misunderstood your original question - it won't be like C# in that we aren't changing the way you code in PowerBuilder. Our intent is to help you migrate as much of your PowerBuilder Win32 code to WPF - so I think we are planning to do just what you're looking for. The migration utility is something we'd like you to test in beta.
Question: Will this presentation be available for download?
Answer: send me an email at and I will get it to you
Question: is the application developed and deployed from PB12 managed code?
Answer: Yes, it's managed code.
Question: Is the Beta 2 Release/Upgrade the same as the “Beta 2 Refresh” or are all the updates referred for the “Beta 2 Refresh”, a release/upgrade planned for after the Beta 2 Release/Upgrade?
Answer: So beta 2 is different from the beta 2 refresh. the refresh is as you expected, bug fixes and CRs to the beta 2 software release
Question: Can we say in order to get best of .NET framework, we have to rewrite our legacy PB program again?
Answer: It really depends upon how well your application is written. Our goal is to make leveraging .NET as easy as possible, which is why we have a migration utility to bring your Win32 code to .NET. If you've written a well partitioned application, and you now would like to leverage services available in the .NET framework, you should be able to do so with relative ease. It's hard to answer because people build so many different types of applications with different coding styles.
Question: Does Beta 2 work with VS 10 Beta ?
Answer: We are building PowerBuilder on top of the shell so you wouldn't use Visual Studio with PowerBuilder.
Question: Will there be support for PFC migration? Or should we scrap PFC and re-write?
Answer: Engineering is migrationg PFC applications during the development process and will be documenting the process and we will make this available in a "how -to" doc format for customers before GA.
Question: will PB still be generating PCode when compiling the objects?
Answer: PB.NET translates to C# as an intermediate step, and that C# is compiled directly to the CLR. There is no PCode with WPF targets.
Question: Future - How long will Sybase continue support for the “Classic” IDE, in reference to PB 12 .Net vs PB 12 Classic? What is Sybase’s direction/mission/vision in this matter?
Answer: We don't have any plans to discontinue any support for Win32. Our current plans are to support version 12 as a complete release, that is, we will support it in the same fashion that we have done in the past for all other releases, it will have a specific lifetime. But, I think Win32 is at the root of your question, and MS does not have plans to discontinue support for Win32 applications, and we will continue to follow their lead in this area.
Question: It is possible to build a Mixed solution where some of the projects are developed in ant others in VS 10 ?
Answer: Yes
Question: I will try my question a different way. If we have an existing C# WPF application that is written in Visual Studio, can we integrate windows created in PB.NET (in order to leverage our legacy PB Classic code that was ported to PB.NET)? More specifically, could we launch a PB.NET window from a menu (or action) inside of a C# WPF application written in Visual Studio? This way we can integrate the two environments seemlessly to the end user.
Answer: The short answer is this is not supported.
Question: Do you support Silverlight as well?
Answer: We will be providing support in a future release - MSOFT is adding an IDE for Silverlight support in their next release of VS.
Question: May I have a copy of slides of today's presentation?
Answer: Send me an email at for the slides
Question: What prevents it from being supported (calling PB.NET WPF windows from an action written in a C# WPF application)? This is critical to our integration of multiple environments.
Answer: The only scenario we currently support for deploying PB objects and using them from another .NET language is the .NET Assembly target, and in that case I believe we are only supporting non-visual objects. While
Question: Does Sybase have plans to support deploying applications as SilverLight?
Answer: That is our current plan for a release post -v12.
Question: I can export dw to PDF without ghostscript
Answer: We are supporting MSOFTs implementation of PDF
Question: What is the target release date for PB12?
Answer: Currently it's in the latter part of the first half of 2010. Likley Q2 2010
Question: Are there 2 types of richTextedit datawindows in PB 12 or only the WPF type?
Answer: There is support in both WPF and Classic but they have different providers; in Win32 we have a specific OEM control built into the product and in WPF we use WPF natively.
Question: For 2010 budget planning - Currently we are planning to continue in your PB 12 .Net Beta program, while maintaining our PB 9.0 development environment. What will be the basic/base cost in 2010, for old classic PB developers to make this leap?
Answer: It would simply be the cost of new development licenses for v12 - $2995/seat is the list price.
Question: Can you use standard .NET WPF controls inside of PB.NET or do you have to use ALL of the PB.NET WPF controls?
Answer: You can use both.
Question: Do we have support for LINQ? Is PB 12 IDE is extensible?
Answer: LINQ is not supported in 12. The PB.NET IDE is extensible, but it depends, so let us know what specifically you have in mind.
Question: are there runtime licensing fees for 12.0?
Answer: No, only developer licenses.
Question: How can I use DataWindow in a VB program?
Answer: DataWindow .NET is available as a plugin for Visual Studio.
Question: For future budget planning - Once a new PB v12 .Net development licenses has been purchased (“$2995/seat is the list price”), what will be the annual maintenance costs?
Answer: The best deal is to purchase a USP (upgrade subscription @$645 annually.) This will give you a new release if it is delivered within 12 months of your purchase, and you can renew it annually for the same fee; two years of USP is still less than an update license. There are other options available for support.
Question: Is PB 12 supported on 64-bit Windows OS during the beta?
Answer: yes, for deployment
Question: what about 64-bit support for the development environment?
Answer: It will likely run but it is not something we test.
Question: going to the xml-fo, now that pb 12 can create pdf without ghostscript, can i feed it xml-fo and have it create a pdf file, i.e. acting like a fop
Answer: Likely not - the FOP processor is Java-based, while PB12's PDF generation is using the .NET Framework.
Question: is the .net framework required for pb 12
Answer: Yes, 3.5, but we redistribute.
Question: Is multi-threading supported in PB12?
Answer: I don't believe there is anything preventing you from using the .NET Framework Thread object within PowerScript. It should translate during our 'pb2cs' compile.



At September 30, 2010 at 5:16 PM , Blogger Nelson said...

Nice Post about PowerBuilder Development . Thanks for sharing few of information .

At August 8, 2013 at 2:06 AM , Anonymous peterjonathan said...

PowerBuilder 12 includes several major Powerscript language enhancements to make development faster and easier than ever. Migrate PB Applications


Post a Comment

Subscribe to Post Comments [Atom]

Links to this post:

Create a Link

<< Home