dot net vs. powerbuilder?

  • Thread starter Thread starter VMI
  • Start date Start date
V

VMI

In a few days I'll be working with a client that uses powerbuilder to
develop applications. I know how to use PB, but I prefer dot net. What can
I say to convince the client that dotnet is a better development tool than
PB? As far as I know, these will be windows applications.
In terms of support, I know there's more help for C# than PB. And I
remember that with PB, trying to debug something was a pain in the butt.

Thanks.
 
i started writing an answer to this, but it was going to be v long.

C# is a language for the .NET platform, which rocks.

PB is a bloated 4GL

I'm currently porting over an enterprise system from PB to C#.

Whist I haven't used the very latest version of PB, and I had a quick read
of the Comparison previously posted (on sybase site); the need for rapid
application development (RAD) tools like PB is fast diminishing. I can
knock far more complicated developments out in C# faster than PB. Aside from
the fact there's already a wealth of code examples, C++ code which you can
port, newsgroups like this one, the LANGUAGES (plural) are better, the .NET
framework offers a whole lot more, it's almost cross platform, (see Mono),
the list goes on.

Thats without mentioning VS.NET. Intellisense changed my life ;o)

All that said (from a develops perspective), if your client has already got
a load of stuff already in PB, he aint going to change it all cos you say
so. Plus the fact, it's going to be expensive redeveloping it all.

just my thoughts
sam
 
Speaking as a Powerbuilder coder trying to dive into C# is very difficult.
Sybase has newsgroups that may help you with your answer
(forums.sybase.com). If you are building windows apps and data driven, I
would think the company would stick with PB, especially if you are adding on
to the application. If you can convince them to code for the Web, then C#
is the way to go. Maybe 3-5 years from now, they will need these
applications on the web. Yes PB is a hog but creating data driven
statements with the DataWindow is a snap. My biggest problem in C# is
binding all the fields if you want to display anything other than a grid
format. But that's another thread.

Mike
 
VMI said:
In a few days I'll be working with a client that uses powerbuilder to
develop applications. I know how to use PB, but I prefer dot net. What can
I say to convince the client that dotnet is a better development tool than
PB? As far as I know, these will be windows applications.
In terms of support, I know there's more help for C# than PB. And I
remember that with PB, trying to debug something was a pain in the butt.

Thanks.
Click to expand...

I don't know if you are aware of this, but the latest PowerBuilder
targets the .NET framework in its compilation. So maybe you don't have
to switch after all.
 
Back
Top