Migration and Upgrade Center

Why Should I Modernize My App?

Experienced developers know that retaining users can be a challenge, so they continuously invest in making their applications faster, more functional and more user-friendly. This effort isn't for the user alone - cleaning up unused and inefficient code makes it easier for the developer to maintain apps moving forward.

Windows 7 Support Expired on January 2020. Don't get left behind when your users migrate their desktops to Windows 10. Now is the perfect time to leverage the latest Windows 10 capabilities and plan for future Windows platform support.
Cross-platform Apps are Necessary. With 73% of internet users turning to their mobile device first, depending on a desktop-only application model limits the usefulness and reach of your app.
Attract Users with Sleek UIs Users abandon apps that look outdated or aren't optimized for their device. Now's the time to wow your users with a design update, made easy with VCL and FMX visual frameworks.
Refactor and Optimize Code It happens over time... code written ages ago becomes clunky or no longer useful. Take the time to optimize your code and you'll reap the reward of faster updates, easier maintenance, and better app performance.

Where Should I Start?

Modern apps have sleek UIs that are intuitive to users, are fast performing, and are written to facilitate continuous integration and deployment.

Watch the webinar on Planning and Completing Your Delphi Migration (1 hour)

Watch the webinar on Migrating and Modernizing C++ Apps (1 hour)

Yesterday's Tools Won't Cut It

You've made the right choice to modernize your legacy apps! In order to be successful, you'll need to upgrade to the best developer tools available today: RAD Studio 11 Alexandria.

Mobile App Support in all Professional, Enterprise and Architect editions enable developers to easily support iOS and Android native apps via one codebase and easily create mobile app UI designs with FMX.
Updated VCL framework. Design modern Windows UI/UX with support for high DPI capabilities, modern styling, and unmatched responsiveness.
Implement the best Windows native support features (better than Microsoft itself!)
Reuse your code to create high-performance micro-services and/or take advantage of containerization
Ensure no deterioration in application performance with proven frameworks
Enhance data integration with new connectivity options
Create Web Clients by leveraging our latest REST API technology
Leverage existing developer skills and save effort and time migrating code, without a painful re-write required for other languages.

Learn more about specific application migration strategies and technologies below, or get RAD Studio now.

Unicode

Unicode support was added to RAD Studio, Delphi and C++Builder starting with the 2009 version. Many migration resources were developed at that time but are still useful today if upgrading from a pre-Unicode (2007 or earlier) version.

Delphi has made migration over the decades relatively painless, however, this doesn't mean it's always effortless and Unicode is one area where some attention may be required!

First, some good news, is many cases legacy Delphi applications that convert to the current Delphi version do so with few or no modifications. If you are working primarily with VCL components (whose support for Unicode has in most cases been considered carefully), or components from third-party vendors who have taken the time to understand the implications of Unicode support, you have an advantage.

Don't panic if you use "millions of strings" in your application, it does NOT mean you have to change any code at all

Unicode Technical Overview

What determines the need to make any Unicode changes is how you're using strings and for what purposes. If you're not doing heavy text processing or manipulations and stick to the standard string operations, mostly likely your code will simply just work. Additionally, just because you have lots of string literals in your code that also doesn't necessarily mean you have to make any code changes. The most common things that you do have to watch for is file I/O and interfacing with external non-Delphi libraries and/or DLLs.

Unicode Resources

As a start, look at these great white papers, technical articles, videos and migration tools to help you out with Delphi and Migration to Unicode:

Delphi and Unicode This white paper has been written to help developers that are using versions of Delphi or RAD Studio that were released previous to the launch of Delphi 2009. Read this paper if you are looking for more information on why and how to Unicode-enable a codebase that has been developed using a pre-Unicode enabled version.

Download the free white paper now

White Paper: Delphi Unicode Migration for Mere Mortals

Stories and Advice from the Front Lines

Whether you are in the early planning stages of migrating an existing application to Unicode-enabled RAD Studio, or in the midst of the process, Delphi Unicode Migration for Mere Mortals can help. Written with input from many of the leaders in the RAD Studio community, this white paper provides you with valuable techniques and advice that will smooth the way.

Download the free white paper now

Webinar: Migrating Legacy Applications to Unicode-enabled Delphi with Cary Jensen

Cary Jensen has worked with Delphi developers around the world - including noted authors, leading third-party vendors, and front line developers - to learn how they approached their Unicode conversions, what challenges they faced, and what solutions they employed. Learn best practices for migration to Unicode in this informative webinar.

Migrating your legacy C++Builder applications to unicode

Featured Blog

Dr. Bob's Unicode page and 8 Unicode Tips - Covers Unicode format and different string types

docwiki

Popular Unicode article in the online documentation at DocWiki discusses "Unicode in RAD Studio"

Unicode Statistics Tool

Unicode Statistics Tool on your Delphi application and check if any Unicode changes are needed.

This Unicode Statistics Tool will assist you in collecting useful statistics for the time and effort needed to migrate your Delphi applications to Unicode.

The tool reviews your code and tells you where and what you will most likely have to change. This will at least give you an estimate of how many lines need to be reviewed.

NOTE: The Unicode Statistics Tool does not know if any of your lines of code really needs to be modified or replaced at all. It does tell you have at least some number of lines you should take a quick glance at. It could be as little as 0 changes needed. It really all depends on how you are using Strings and Chars in your application.

The result is Delphi is 100% Unicode. The migration is easy, the Visual Component Library (VCL) and the compiler handle many things.

The tool lists all used units, including Delphi units (and how many times each one was used), number of files, number of lines, and number of instances of String, Read, Write, SizeOf, etc.

Featured Blog

Migrating your project from older versions of Delphi. The Pitfalls
Craig Chapman covers a range of migration topics including

Cross platform migration
Windows 64bit
Unicode migration

Migrating to 64bit

Ever since Delphi XE2, it has been possible to generate Delphi 64bit applications from the same code base as your traditional Windows 32bit Delphi code. The business case for 64-bit for business is covered in this tech paper The Impact of 64-bit Applications to your Company’s Bottom Line

On the whole moving to 64bit (on Windows, but also iOS) is beautifully simple to achieve! It can be just as simple as adding the 64bit target platform in the project manager and rebuilding the project. This is a massive benefit over other languages that need different types declared to resolve the difference between the two platforms.

64bit Resources

Building 64bit Applications with Delphi

Overview of how to build 64-bit Delphi applications with this short tutorial.

[7m16sec]

Featured Blog

Delphi 64bit Code by Stephen Ball covering what is the same, what is different, predefine conditional compiler options and using assembler code.
Delphi 64bit code

docwiki

Converting 32-bit Delphi Applications to 64-bit Windows

Migrations of Database and Middleware

Migrating from the Borland Database Engine (BDE) or DBExpress

The Borland Database Engine (BDE) has been deprecated, and beginning with version XE8 the BDE has been removed from the Delphi installation, but is still available as a separate download from Code Central. All applications using the BDE are recommended to be migrated to FireDAC. If you are new to FireDAC Data Access Components, start here and look at the First Steps and Getting Started links.

dbExpress is also in maintenance only mode and users should look to migrate to FireDAC which offers more databases, is faster and provides more features.

Database Resources

FireDAC Skill Sprints - Migrating BDE applications to FireDAC and InterBase - David I

Featured RAD Studio tool reFind

Using reFind you can convert your code automatically from BDE to FireDAC, including updating uses clauses, field definitions.

docwiki | Blog

DocWiki Migrating dbExpres to FireDAC

This article provides a tutorial showing how to migrate a simple client-server application using dbExpress data access components, such as TSQLConnection, TSQLQuery, TSQLTable, to FireDAC
docwiki

Delphi Parser

An alternative to reFind, a Free Evaluation Edition of The Automatic Migration Scripting Wizard For Converting Legacy Delphi BDE Code to FireDAC
Delphi Parser BDE to FireDAC migration tool

FireDAC Skill Sprints is a series of 12 x 20minute videos teaching you the advanced features of FireDAC

Entire video playlist.

Migrating 3rd Party Components / Libraries

What 3rd party libraries (components) are you using in your older Delphi?

The 3rd party plug-ins (libraries) need to be rebuilt in the current Delphi version. Having the source code makes this easier. You will need to re-compile your 3rd party components / libraries from older Delphi using the current Delphi version so the components and libraries can be used in current Delphi projects.

Any 3rd party components / libraries without the source code may need updated versions for the current Delphi version.

The current Delphi includes the new Getit Package Manager to allow you to browse, download, purchase, and install GetIt packages into the current Delphi version. GetIt currently includes popular free packages such as libraries, components, IDE extensions, and SDKs, like Open Source "TurboPack" Components, JEDI Visual Component Library, etc., certified to work in the current Delphi version!

10 Tips For Making Your Mobile App Succeed

Monetize Your App Using In App Payments And Ads

Ads are a good way to monetize your apps. Use full screen interstitial ads at the start of your app and at natural stopping points. Integrate leaderboard ads (320x50) into either the header or footer where it makes sense for your interface. Over at AppBrain Stats they have a list of the most popular ad networks that include Admob, Millennial Media, InMobi, Chartboost, Tapjoy and many more. Add in-app payments for consumable, one time purchase, and subscription-based revenue. Offer both a paid version with no ads and a free version of your app. Provide a way to disable ads in the free version via an in-app purchase.
Secure Your App’s Data Connections With SSL

Mobile users are more mobile than ever these days and they jump from secured wireless access point to 4G to unsecured wireless hotspot multiple times per day. If you want to keep your user's data secure from the prying eyes of just about anyone using a network packet sniffer you will want to implement industry standard encryption like TLS/SSL (Transport Layer Security/Secure Sockets Layer). Using a good tried and true third party library is the way to go.
Encourage Users To Rate Your App

A good rating in the various app stores is more important than ever. Usually only people who want to give your app a low rating end up on app store rating pages and rate your app down. You can encourage users who love your app to rate your app by pointing them in the right direction. The third time a user uses your app is good time to ask them to visit the rating page for your app on the app store of your choice.
Create And Deploy Icons For Your App

Having a great looking icon is a must have to increase your chance of success in the app stores. There are more than 30 different icon sizes that you need to create and deploy for Android and iOS apps. This can be a real chore to create all of the icons needed. There are utilities out there that can help you do that like Mobile Gfx Setup, Paint.net and Adobe Flash CC is a more advanced commercial Windows program that comes with a free trial and you can create and export your icons pretty easily in it as well.
Handle App Activate And Deactivate Lifecycle Events

Once you have the features in your app all finished you aren't done. One reason why some apps succeed and others do not is because of the polish that goes into them. There are events on both Android and iOS which will tell your app when it becomes active or goes into the background. You should find and handle these events so that your app has a slick user experience. Test and handle all of the various actions in your app like going into sleep mode and coming back out or pressing the back button.
Don’t Fly Blind. Add Analytics To Your App

Implementing analytics using various third party analytics libraries like Google Analytics, Flurry Analytics, GameAnalytics and Parse Analytics to name a few. Analytics providers have their own Android, iOS, and REST SDKs that you can integrate. Track important data points like how long a user uses your app, which screens do they use to most, and where they may get stuck or leave your app. Most important of all is to take action on the information that the analytics give you. Iterate and test. Iterate and test.
Setup Push Notifications

Push are an important mechanism for keep your users engaged with your app. Try to find a balance between sending too many and not sending enough push notification to keep users engaged. Android push notifications are available through Google Cloud Messaging. iOS push notifications are available through the Apple Push Notification Service. Implementing push notifications can be tough but third party providers like Parse, PushWoosh, and Upsight (formerly Playhaven) make it easier for you.
Use Threads To Keep Your App Responsive

Threads allow you to execute long running procedures in a separate process. Use threads anywhere your app would block user input like uploading and downloading files, processing information or loading data. If your app appears frozen users may exit and move on to the next app. If a user is sitting on a screen waiting for something to happen, think about how you can rearchitect your app so that the event they are waiting for happens in the background instead.
Check Network Connectivity Before Trying To Connect

Mobile device connectivity is not a sure thing. If your app needs internet access you need to handle the scenario when connectivity is not available. Using queuing systems for uploading and downloading data. Implement file download resuming where possible. An offline mode where online only features are disabled while connectivity is unavailable may be a good idea.
Optimize Your App Name, Description and Distribution

Choose a functional name, descriptive, or a unique name (or a combination) to help your app succeed. Stay away from trademarked terms. A good description that lays out what your app does, who your competitors are and what technologies you used to build it can help people find your app. Building your app is just the beginning. Distribution is also key to a successful app so make sure if your app runs on both Android and iOS that you deploy it to the biggest app stores like Google Play, Apple App Store, Amazon Appstore, and Samsung Apps. Each app store has their own submission process and guidelines but the extra boost in users you get is worth it. You may just find your niche on the Amazon Appstore or Samsung Apps.

The default string in Unicode Delphi is the new UnicodeString type. By default, the UnicodeString type will have an affinity for UTF-16, the same encoding used by Windows. This is a change from previous non-Unicode versions which had AnsiString as the default type. The Delphi RTL has in the past included the WideString type to handle Unicode data, but this type is not reference-counted as the AnsiString type is, and thus isn't as full-featured as Delphi developers expect the default string to be.

For the newer Unicode versions of Delphi, a new UnicodeString type has been designed, that incorporates the capabilities of both the AnsiString and WideString types.

A UnicodeString can contain either a Unicode-sized character, or an ANSI byte-sized character. (Note that both the AnsiString and WideString types will remain in place.)

The Char and PChar types will map to WideChar and PWideChar, respectively.

Note, as well, that no string types have disappeared. All the types that developers are used to still exist and work as before. However, for Unicode Delphi, the default string type will be equivalent to UnicodeString.

In addition, the default Char type is WideChar, and the default PChar type is PWideChar.

That is, the following code is declared by the compiler:

type
string = UnicodeString;    Char = WideChar;   PChar = PWideChar;

With the addition of Unicode as the default string, Delphi can accept, process, and display virtually any alphabet or code page in the world. Applications you build with the newer Unicode versions of Delphi will be able to accept, display, and handle Unicode text with ease, and they will work much better in almost any Windows locale.

In current Unicode versions of Delphi, 'Char' and 'PChar' are now 'WideChar' and 'PWideChar'. You cannot assign an AnsiChar/PAnsiChar to a WideChar/PWideChar, and vice versa, without extra coding.

In any case, such code is redundant in current Unicode Delphi anyway, since AnsiString is now codepage-aware. You can assign any AnsiString-based string type (as AnsiString can be typedefed with a specific codepage at compile-time) to a WideString or UnicodeString, and the RTL will convert the characters to UTF-16 automatically for you.

If you really want to keep the code, then at the very least you should change the AnsiString parameter to a RawByteString (so that it can accept any codepage-specific AnsiString), and then use the new StringCodePage() function to know which codepage the character data is actually encoded as.

For example:

function StringToWideString(const s: RawByteString): WideString;
    var
        l: integer;
        cp: Word;
    begin
        if s = '' then
            Result := ''
        else
        begin
            cp := StringCodePage(s);
            l := MultiByteToWideChar(cp, MB_PRECOMPOSED, PAnsiChar(s), Length(s), nil, 0);
            SetLength(Result, l-1);
            if l > 1 then
                MultiByteToWideChar(cp, MB_PRECOMPOSED, PAnsiChar(s), Length(s), PWideChar(Result), l);
        end;
    end;

Which can be simplified to this:

function StringToWideString(const s: RawByteString): WideString;
	begin
	  Result := s;
	end;

One of the most relevant changes since Delphi version 2009 is that String types are now based on Unicode. Previously based on the ANSI standard, the AnsiString and WideString types still work the same way, except regarding their data size in bytes.

Unicode changes, in short:

String maps UnicodeString, no longer AnsiString
Char now maps WideChar (2 bytes, not 1 byte) being a UTF-16 character
PChar maps PWideChar
AnsiString maps the old String type

No changes were applied to:

AnsiString
WideString
AnsiChar, PAnsiChar
Short String contains AnsiChar elements
Implicit conversions still work.

The user's active code page controls the mode (ANSI vs. Unicode), so that ANSI strings are still supported.

Operations that do not depend on character size:

String concatenation
Standard String functions. E.g., Length, Copy, Pos, and so on.
Operators. E.g., , CompareStr(), CompareText(), etc.
FillChar ( )
Windows API

Operations involving the character size (measured in bytes) may require a few changes. Nothing too complicated, but here's a tip: pay special attention to code in which you:

Assume Sizeof (Char) is 1.
Assume the size of a string equals the number of bytes in the string.
Handle String or PChars directly.
Saves or reads a string from/to a file.

Items 1 and 2 do not apply to Unicode, because in Unicode the Sizeof (Char) is 2 bytes and the size of a string is twice as big as the number of bytes. Besides, the code that reads and saves files must understand the right number of bytes to perform those operations, for a character is no longer represented as 1 byte.

Migration and Upgrade Center

Migration and Upgrade Resources for Delphi, C++Builder and RAD Studio

Why Should I Modernize My App?

Where Should I Start?

Yesterday's Tools Won't Cut It

Unicode

Unicode Technical Overview

Unicode Resources

Stories and Advice from the Front Lines

Webinar: Migrating Legacy Applications to Unicode-enabled Delphi with Cary Jensen

Migrating your legacy C++Builder applications to unicode

Featured Blog

docwiki

Unicode Statistics Tool

Featured Blog

Migrating to 64bit

64bit Resources

Building 64bit Applications with Delphi

Featured Blog

docwiki

Migrations of Database and Middleware

Migrating from the Borland Database Engine (BDE) or DBExpress

Database Resources

Featured RAD Studio tool reFind

DocWiki Migrating dbExpres to FireDAC

Delphi Parser

Migrating 3rd Party Components / Libraries

10 Tips For Making Your Mobile App Succeed

Monetize Your App Using In App Payments And Ads

Secure Your App’s Data Connections With SSL

Encourage Users To Rate Your App

Create And Deploy Icons For Your App

Handle App Activate And Deactivate Lifecycle Events

Don’t Fly Blind. Add Analytics To Your App

Setup Push Notifications

Use Threads To Keep Your App Responsive

Check Network Connectivity Before Trying To Connect

Optimize Your App Name, Description and Distribution

Unicode Technical Overview

加入我们的全球开发者社区