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
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
Connect with Us