🚀 go-pugleaf

Hi Colin,

I think a move from BCB3 to BDS2006 will *as difficult* as a move to BCB6, for different reasons. I did it - in a slightly different manner - went from BCB3 to BCB5 to BDS2006. The first jump was the hardest - took a long time removing extraneous OWL calls, whereas the second jump was fraught with project file nightmares. 

In conclusion, expect difficulties. However, the inclusion of codeguard makes it worthwhile, in my humble opinion.

mat. 

Colin B Maharaj <noreply@myhost.com> wrote:
>Hi all, once again I am budgeting to purchase BDS2006 for the BCB 
>portion. I did purchase the BCB6 Enterprise but I was not able to 
>successfully port all my BCB3 code to the 'new' environment.
>
>Actually it is a question of time - I do not have.
>
>If I hear that I can go from BCB3 to BDS2006 easily (easier than BCB6)
>I will get my manager to look at the purchase seriously.
>
>So...
>Will I get a better migration path to BDS2006?

"Colin B Maharaj" <noreply@myhost.com> wrote in message
news:44153e46$1@newsgroups.borland.com...

> I did purchase the BCB6 Enterprise but I was not able to
> successfully port all my BCB3 code to the 'new' environment.

Why not?  Please be more specific.  If you are having problems porting to
BCB6, then you will have problems porting to BDS as well.

> Will I get a better migration path to BDS2006?

Doubtful.  Other than a few bug fixes, the compiler/linker in BDS are the
same as in BCB6.  And BDS is a completely new environment over the previous
BCB product line, so you'll have to re-make your projects anyway.


Gambit

Remy Lebeau (TeamB) wrote:

> 
> Why not?  Please be more specific.  

There is really no good reason as to why this is so, just a lot of work 
I have to do..

> Doubtful.  Other than a few bug fixes, the compiler/linker in BDS are the
> same as in BCB6.  And BDS is a completely new environment over the previous
> BCB product line, so you'll have to re-make your projects anyway.
> 
How about if I use a third party tool to convert my form to text and use 
the text versions. Is this going to make any difference?

"Colin B Maharaj" <noreply@myhost.com> wrote in message
news:4416a05d$1@newsgroups.borland.com...

> How about if I use a third party tool to convert my form to
> text and use the text versions. Is this going to make any difference?

That is not necessary.  BDS supports the same binary DFMs that earlier
versions did.  What you will have to be careful of, however, is that a lot
of new properties have been added to TForm since BCB 3, and some of those
properties are going to default to behavior that you may or may not want.
Watch out for the OldCreateOrder property in particular.  If your code is
using the OnCreate event, then the OldCreateOrder property can really mess
up your form's run-time initialization.

In any case, I STRONGLY recommend that you NOT try to import your existing
BCB 3 projects into BDS.  Like in earlier versions, BDS also has its share
of problems importing project files.  You should create new projects in BDS
fresh, and then migrate your existing code over to them.


Gambit

Colin B Maharaj wrote:
> Hi all, once again I am budgeting to purchase BDS2006 for the BCB 
> portion. I did purchase the BCB6 Enterprise but I was not able to 
> successfully port all my BCB3 code to the 'new' environment.

	Depends on what your issues were?

> Actually it is a question of time - I do not have.

	Most of us don't.  ;-)

> 
> If I hear that I can go from BCB3 to BDS2006 easily (easier than BCB6)
> I will get my manager to look at the purchase seriously.

	I've done the jump to every version except BCB6.  (Went from BCB5 -> BDS2006)
As a RULE, not a suggestion, RULE these are my steps -- I have never seen a successful conversion in any of my projects, 
that doesn't take longer to fix then to create a new project:

1. Copy the complete project to another directory.
2. Open BCB and open your copied project.
3. Open BDS and do File->New C++ Builder Project
4. Use BCB to show you which files you need to add to it.


> Will I get a better migration path to BDS2006?

	Probably not, as I mentioned before -- Project conversions between BCB versions and between BCB to BDS are fraught with 
failures.  It is MUCH, MUCH easier (and less hair pulled out) to create a new project and just add all the needed files 
using the old version as your guide.

Nathan.