Documentation on moving D6 components to D2007?
Paul Hope
Is there any documentation on moving components from D6 to D2007 vcl. I
have quite a few now unsupported components for which I have the source but
I am worried I may not the expertise to move them if the process is
difficult.
Regards
Paul
Greg Hunter
"Paul Hope" <paul...@allcomm.co.uk> wrote in message
news:472f...@newsgroups.borland.com...
Hi Paul
There are quite a few blogs and articles out there, such as
http://www.shorterpath.com/develop/zonearticles/vcltonet.asp this one
(albiet it that one is D8 not 2007, the points are still valid) and
http://bytemonger.blogspot.com/2007/05/delphi-win32-to-delphinet-part-i-geting.html.
There are more out there.
It helps to be aware of these newgroups, and be a dab hand at google as well
:-)
Also companies such as resolvess.com after migration services if you really
do feel that you want to move the stress somewhere else :-)
Am am currently involved in migration of 35 components and about 1/2 million
lines of code app from D6 to D2007, and can vouch for most point in both of
those above links!
Good luck
Greg.
Paul Hope
Thanks for responding - I thought this was another dead end ;-)
I'm just wondering - the blogs you pointed to are referring to .net - I'm
not interested in .net - only vcl. Do these articles still apply?
Regards
Paul
"Greg Hunter" <gr...@resolvetech.co.uk> wrote in message
news:47386b5e$1...@newsgroups.borland.com...
Paul Hope
I installed the evaluation version of D2007 to see how easy it is to migrate
vcl components. The answer - it is easy - there are no big issues.
The process is
1 - copy the source to a new folder. Never open D6 with D2007 - it seems to
screw it up and it cant be used by D6 anymore.
2 - find and edit the source $DEFINEs so that it will handle VER185
3 - check the package library options so that the dcp,dcu and bpl outputs
are not where the D6 ones are and that the search paths are looking for
D2007 versions.
4 - build and install the packages.
Paul
"Paul Hope" <paul...@allcomm.co.uk> wrote in message
news:473f1720$1...@newsgroups.borland.com...
Yogi Yang 007
> I'm replying to myself now.
>
> I installed the evaluation version of D2007 to see how easy it is to migrate
> vcl components. The answer - it is easy - there are no big issues.
>
> The process is
>
> 1 - copy the source to a new folder. Never open D6 with D2007 - it seems to
> screw it up and it cant be used by D6 anymore.
> 2 - find and edit the source $DEFINEs so that it will handle VER185
> 3 - check the package library options so that the dcp,dcu and bpl outputs
> are not where the D6 ones are and that the search paths are looking for
> D2007 versions.
> 4 - build and install the packages.
>
This is easy only and only if you have got the original source. What
about those VCLs that do not come in source but come in precompiled DCUs?
Mike Williams (TeamB)
> What about those VCLs that do not come in source but come in
> precompiled DCUs?
I that case you'll need to get updated DCU files from the original
source of those DCU files. DCU files have always been tied to a
particular version of Delphi and for that reason it's always best to
make sure you have the source code.
--
-Mike (TeamB)
Greg Hunter
> Hi Greg
>
> Thanks for responding - I thought this was another dead end ;-)
>
> I'm just wondering - the blogs you pointed to are referring to .net - I'm
> not interested in .net - only vcl. Do these articles still apply?
>
> Regards
> Paul
>
> "Greg Hunter" <gr...@resolvetech.co.uk> wrote in message
> news:47386b5e$1...@newsgroups.borland.com...
>>
>> "Paul Hope" <paul...@allcomm.co.uk> wrote in message
>> news:472f...@newsgroups.borland.com...
>> > Hello
>> >
>> > Is there any documentation on moving components from D6 to D2007 vcl.
> I
>> > have quite a few now unsupported components for which I have the source
>> > but
>> > I am worried I may not the expertise to move them if the process is
>> > difficult.
>> >
>> > Regards
>> > Paul
>> >
>> >
Hi Paul.
sorry for the slow response, been of the groups for a little while.
sorry I misunderstood, I am deep into a .net migration at the mo, and just
presumed that you were doing the same.
Glad to see you got it sorted :-)
Cheers
Greg.