ASKER
ASKER
ASKER
Delphi is the most powerful Object Pascal IDE and component library for cross-platform Native App Development with flexible Cloud services and broad IoT connectivity. It provides powerful VCL controls for Windows 10 and enables FMX development for Windows, Mac and Mobile. Delphi is your choice for ultrafast Enterprise Strong Development™. Look for increased memory for large projects, extended multi-monitor support, improved Object Inspector and much more. Delphi is 5x faster for development and deployment across multiple desktop, mobile, cloud and database platforms including 32-bit and 64-bit Windows 10.
TRUSTED BY
At the same time I used Delphi 7 for many years as my main dev plateform, and only recently decided to switch to Delphi XE (I was not convinced by intermediary versions like Delphi 2005, 2007 - And 2009, 2010 where a big step. I'll say why in a moment).
But one has to admin that Delphi XE is great.
So, abuot the jump from D5 to XE : it is like a move from Win95 to Vista directly. Most of your applications using standard components will work again with just a few touches and compilation, but some time you'll hit trouble.
First step : the 3rd party components. You'll have to decide which you want to keep, and the ones you'll have to change. Because a lot of standard new components exist now for XE that weren't there at D5 time or that the author didn't want to make compatible with such an old dog. And some are really worth the change.
- make a list of all the 3rd party components you use
- see if the author still exist, and which Delphi version is the last one supported.
if Delphi XE is supported , GREAT ! keep it !
otherwise, 3 possibilities (IF YOU HAVE CODE, OTHERWISE SKIP DIRECTLY TO LOOKING FOR ALTERNATE) :
- Delphi 2009/2010 : That should be just fine, and will only need maybe a few renaming of packages to avoid such bpl names like "WhateverLibrary_2009.bpl"
The main problem (Unicode) is already fixed with such D2009 compatible packages
- Delphi 7-2007 : Most of the components will be Ok, as D7 (maybe even D6) introduced the major changes in component designs that are still used in newer Delphi (with some extensions of course) so if those libraries are not susceptible to Unicode problems, just rename packages if necessary and compile ! Working ? Great ! Not Working ? either you are a good delphi programmer and depending on the problem you might be able to fix it, or the compiler throw pages of errors and warning and you might consider looking for newest alternate solutions.
- Delphi 5 and below : try recompile, if they are not complex lib that might just work. most of the time, it won't and I will recommend forgetting it. It will be a pain already to make those work if you have to fight agains components designs AND unicode, but you will be condemned to maintain those alone for the time to come, without the author.
Now, about the most famous problem when switching to 2009 and above : Unicode !!!
All strings in delphi are now considered UNICODE (16 bits per char) and not ANSI (8 bit per char). And that impacts everything in the VCL. So if your code uses lots of PChar, you'll have trouble.
That particular problem can be difficult to overcome in some cases, but there are plenty How-To to get started by googling a bit, or here in ExEx.