Pino,
If you want an unbiased answer to that, I think this might be the wrong
place to ask. I only know a little of PowerBuilder, so I'm certainly not the
right person to ask. However, I think you might want to look at the future
of both products, the masses behind them (i.e. the number of active
developers), the platforms you need to build on, which technologies, i.e.
desktop or Web, the database which I believe is Sybase ASA ands thus
supported by both technologies. That should be a start. In addition, if you
know any PowerBuilder developers outside your own organization, ask them
what they think. If you can find any current PowerBuilder AND .NET Framework
developers, they should be able to help you get a better picture of what is
right.
Okay, I'm biased so go with .NET... ;-)
--
Carsten Thomsen
Enterprise Development with VS .NET, UML, AND MSF
http://www.apress.com/book/bookDisplay.html?bID=105
"Pino" <pi********************@gmail.com> wrote in message
news:%2***************@tk2msftngp13.phx.gbl...
In our company we are developing new products (distributed applications)
using .NET and SQL Server. However, there are some persons who continue to
work with PowerBuilder and Sybase ASA (Adaptive server Anywhere) for old
applications maintenance (client-server app), but in this period we're
choosing if begin a new application with PowerBuilder or .NET.
What are the differences between the two technlogies? There are any reason
to choose PowerBuilder only for *technologically* reasons?
Thanks in advance,
Pino.