Re: Is D2005 with update 2 worth buying

From: Charles Appel (charlesappel_at_mindspring.com)
Date: 03/17/05 

Date: Thu, 17 Mar 2005 11:30:38 -0500

"Lauchlan M" <LMackinnon@Hotmail.com> wrote in message
news:42398903$1@newsgroups.borland.com...
> > I don't know. I have ported several dozen small applications
> > to it without any major problems. But I have not moved any
> > really large application to it from an earlier version of Delphi.
> > The only way to really find out is to copy the app to a new
> > work directory and try to rebuild the copy in D2005.
> >
> > I'd keep D7 installed just in case.
>
> How would it work going backwards? Say you did some modifications in
D2005,
> and then wanted to go back to D7 or D6.
>
> I presume if you don't use any new syntax, the source is pretty much the
> same and you could open it up in D6 or D7 without introducing any
problems?

I haven't attempted to port a app back down from D2005.
My experience with earlier versions is that porting down is
always harder than porting up. The earlier versions of Delphi
are bothered by new properties for the controls. Sometimes
the projects compile fine anyway. Sometimes they don't.

I have just finished developing a new series of poker libraries
for Delphi. (They are in final testing now.) For this project, I
did the initial development in D4. When that was complete, I
copied the ".pas", ".dfm", ".dpr", and ".res" files to new
directories for D5, D6, D7, D2005 W32, and D8. I didn't
run into any problems. I then made the changes necessary for
D8 and copied those files into a new directory for D2005 .NET.

Here I ran into some problems - probably caused by the contents
of the ".bdsproj" files. I solved this by deleting the the contents
of the D2005 work directory and recopying the project without
the ".bdsproj" files. I have experienced similar problems when
moving a D2005 .NET project into D8. 

-- 
Charles Appel
"A generation which ignores history has no past - and no future."
      Robert Anson Heinlein

Relevant Pages

  • Updates on Delphi 8 stuff
    ... The Delphi 8 for Microsoft .NET project is now visible in ... project entry is currently named "Delphi.NET" as it is a different ... hierarchy than the Delphi Win32 code base. ... borland.public.bdn.qualitycentral newsgroup, where follow-ups to this ...
    (borland.public.delphi.non-technical)
  • Re: Delphi.NET vs C#: is Delphi.NET compelling?
    ... that you can mix your languages and use the individual language strengths to ... He noted in one of his courses that Delphi ... > none of the other languages in this discussion have. ... > brand new project, and it is a .NET project, what reasons might be ...
    (borland.public.delphi.non-technical)
  • How to write Delphi 2005 XML-style project files (.bdsproj)?
    ... with Perl? ... I've tried XML::Simple, I manged to read the XML file, but after writing ... Delphi doesn't recognize it any longer. ... some "magic bytes" in the first line of the .bdsproj file, ...
    (comp.lang.perl.modules)
  • Re: So Long and Thanks for all the Fish!
    ... FWIW, we're about to start a new Delphi for .NET project. ... compelling reasons being that we already know Delphi very well, ...
    (borland.public.delphi.non-technical)
  • Re: Code healer unable to make a project analysis
    ... Are you trying to analyze a Delphi for .net project? ... CodeHealer doesn't support this yet (I believe the next version ...
    (borland.public.delphi.thirdpartytools.general)