 |
BorlandTalk.com
Borland discussion newsgroups
|
| View previous topic :: View next topic |
| Author |
Message |
Thomas Blankschein
Guest
|
 Posted: Sat Dec 24, 2005 7:33 am Post subject: Migration from BCB5 to BCB2006/BDS? |
 |
|
Hello,
we have a lot of applications, packages and little tools developed in BCB5.
We think of buying the BDS including BCB2006. How about migration? As far as
I learned yet, it's good to build up the projects new from scratch and add
the units and forms from the BCB5 projects. But how about the newer vcl? Are
there any heavy difficulties in converting the things? Because there are
several years in development between the two products.
Thanks,
Thomas
|
|
| Back to top |
|
 |
Andrue Cope [TeamB]
Guest
|
| Posted: Tue Jan 03, 2006 9:35 am Post subject: Re: Migration from BCB5 to BCB2006/BDS? |
|
|
Thomas Blankschein wrote:
| Quote: | How about migration? As far as I learned yet, it's good to build up
the projects new from scratch and add the units and forms from the
BCB5 projects.
|
Actually BDS2006 seems a lot better in this area than prior versions. I
would suggest just importing the project and tweaking it a bit first.
| Quote: | But how about the newer vcl?
|
There are some changes that will impact you as a result of missing out
BCB6 but they are mostly namespace changes.
--
Andrue Cope [TeamB]
[Bicester, Uk]
http://info.borland.com/newsgroups/guide.html
|
|
| Back to top |
|
|
Roddy Pratt
Guest
|
| Posted: Tue Jan 03, 2006 12:20 pm Post subject: Re: Migration from BCB5 to BCB2006/BDS? |
|
|
"Andrue Cope [TeamB]" <no.spam (AT) not (DOT) a.valid.address> wrote
| Quote: | Thomas Blankschein wrote:
How about migration? As far as I learned yet, it's good to build up
the projects new from scratch and add the units and forms from the
BCB5 projects.
Actually BDS2006 seems a lot better in this area than prior versions. I
would suggest just importing the project and tweaking it a bit first.
|
Yes, it's not too bad. However I've hit QC23034 twice, which wasn't
obvious...
One thing to note is that each tool (C Compiler, Linker, TASM, Pascal
Compiler, Resource Compiler) has a separate include path, so you may have to
fettle things quite a bit.
I haven't found a way of having 'overall' include paths for all tools, and
then just overriding on a per-tool basis if necessary. That would make
conversion much easier.
- Roddy
|
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
FAQ
Search
Memberlist
Usergroups
Register
Profile
Log in to check your private messages
Log in
