Watch, Follow, &
Connect with Us

For forums, blogs and more please visit our
Developer Tools Community.


Welcome, Guest
Guest Settings
Help

Thread: Migrating Projects



Permlink Replies: 2 - Last Post: Jan 25, 2018 2:34 AM Last Post By: Goran Ekstrom
Robert Penoyer

Posts: 15
Registered: 2/14/06
Migrating Projects
Click to report abuse...   Click to reply to this thread Reply
  Posted: Jan 24, 2018 5:57 PM
A page on the Embarcadero site contains this statement:

"Don't let C++ Builder 10 Seattle convert your older Builder project.
Copy your files into a new folder, create a new project and add your
source files to it."

(See Item 1 under "Tips for migrating legacy C++ Builder to C++
Builder 10 Seattle" at https://tinyurl.com/ybtmox2f)

I've seen Remy Lebeau say something like this many times but I don't
know the steps involved.

Since Embarcadero published the quoted statement, it must be official
Embarcadero policy. Has Embarcadero published a procedure for doing
the migration?
Mark Richards

Posts: 42
Registered: 12/8/99
Re: Migrating Projects
Click to report abuse...   Click to reply to this thread Reply
  Posted: Jan 25, 2018 1:55 AM   in response to: Robert Penoyer in response to: Robert Penoyer
I would do exactly as it suggests:

Create a new folder and copy your source code files into it, excluding the project files

Launch the IDE, create a new project and configure it how you want it (path, options, version etc) BEFORE you start adding your source code files to the project.

It saves a LOT of migration issues, especially with paths, and packages (design time even if you don't compile with them the old ones were referenced in your original project file, missing lib / bpl / dll files due to the newer versions having renamed them e.g. important190.bpl may now be important240.bpl

Robert Penoyer wrote:
A page on the Embarcadero site contains this statement:

"Don't let C++ Builder 10 Seattle convert your older Builder project.
Copy your files into a new folder, create a new project and add your
source files to it."

(See Item 1 under "Tips for migrating legacy C++ Builder to C++
Builder 10 Seattle" at https://tinyurl.com/ybtmox2f)

I've seen Remy Lebeau say something like this many times but I don't
know the steps involved.

Since Embarcadero published the quoted statement, it must be official
Embarcadero policy. Has Embarcadero published a procedure for doing
the migration?

Edited by: Mark Richards on Jan 25, 2018 1:55 AM
Goran Ekstrom

Posts: 149
Registered: 1/10/04
Re: Migrating Projects
Click to report abuse...   Click to reply to this thread Reply
  Posted: Jan 25, 2018 2:32 AM   in response to: Robert Penoyer in response to: Robert Penoyer
I've seen Remy Lebeau say something like this many times but I don't
know the steps involved.

The way I do it is that I have separate parent folders for each version of RAD Studio, e.g. "BerlinWork\parent project name\projects...", "TokyoWork\parent project name\projects...".

When I migrate a Project I start with creating a folder for the new RAD studio version, then a blank Project for that folder, preparing all the compiler options, specifying the correct Project name, creating a main form with the same name as in the Project to be migrated. When that blank Project compiles OK I copy the source only from the old to the new Project folder.

There will be two file name collisions, the ProjectName.cpp and the MainForm.cpp files. I rename the orignal ProjectName.* files and use the RAD editor to move any custom code to the new ProjectName.* files to preserve the main code created by RAD studio.

Next I Close the Project, replace the new and blank MainForm files with the original ones and re-open the Project. There is usually some issues with third parties that need solving.

Finally I add the remaining modules and make sure all compiles.
Legend
Helpful Answer (5 pts)
Correct Answer (10 pts)

Server Response from: ETNAJIVE02