Re: Is it worth upgrading from Delphi 7 to Delphi 2005/2006?

Ryan McGinty wrote:

> > For Win32 products, I'd have to say no. I think you might as well
> > stay with Delphi 7.
>
> You might think that, but that is obviously because you don't use (or
> find use for) half features of D2006. If you feel that D7 is "as
> good" then I must assume that:
>
> 1) You don't have a large project with multiple DLLs/BPLs

Correct. One or two medium sized apps with an external DLL.

> 2) You don't have to debug a project with DLLs/BPLs

Correct.

> 3) You don't use StarTeam and thus find no value in the StarTeam
> integration

Correct.

> 4) You aren't interested in class diagraming and
> refactoring in Together

I'd have to read up on it first.

> 5) Don't care about all the cool new editor,
> IDE, and debugger enhancements

Is there a list of new features of the new editor somewhere?

The IDE appears clumsy compared to D7

Debugger enhancements? It's still behind Visual Studio.

> I recently had to debug a package based on a package based on a
> package. In D7 I might be able to debug it with breakpoints once
> before it either stops responding or stops breaking. In D2006, not
> only did it work EVERY time without restarting, it worked faster than
> I've ever seen Delphi debug. There are several things that are
> faster in D2006 than D7 (compile times, opening project options, code
> completion, start up times w/ Win32 only). I have yet to find
> ANYTHING that is slower on my machine and if it is, it is so
> negligible that I've not noticed. Granted, I do not have 2000
> components installed, but I do have 500+ and notice no issues at all.
> It is also about as stable as any product that I've seen.

I'm debugging an ASIO application which has problems if I hit RESET in
D7 or D2006. In either case, the IDE hangs, as does the debugee.
Sometimes psshutdown works, sometimes not. I've logged this as a bug,
but it's related to hardware.

> So, yeah, if you don't want to be more productive and you think that
> D7 has little room for improvement because you don't use any of the
> advanced features, then ok, it is about the same... I however,
> cringe when I have to fire up D7 to make a change to our current
> release's codebase. I would NEVER go back to it. Just my opinion.
>
> Ryan

More productive?

--

Pete Goodwin
.

Relevant Pages

  • Re: Component
    ... debug it, ... In your main Delphi instance -- the one you're using to develop the ... Then "run" the package. ... create the component from within your form's OnCreate handler, ...
    (comp.lang.pascal.delphi.misc)
  • Re: How to debug com+ component in delphi?URGENT
    ... > Assuming you have already created a COM+ component in Delphi, ... > the Include remote debug symbols option. ... > Locate the COM+ application under Component Services | Computer and open its ... You can try EurekaLog. ...
    (borland.public.delphi.ide)
  • Re: Delphi in a VM ..... VirtualPC 2007, VMWare 6 or ...?
    ... basic installation, all is OK. ... | doesn't have Delphi so I couldn't debug using that one... ... | Moving Delphi into a VM, or at least having a copy of Delphi in a VM ... | My notebook has 2 gigabytes RAM and a Core2Duo with virtualization ...
    (borland.public.delphi.non-technical)
  • Re: Delphi in a VM ..... VirtualPC 2007, VMWare 6 or ...?
    ... Arthur Hoornweg wrote: ... Recently I had to debug a communications protocol and I couldn't ... Moving Delphi into a VM, or at least having a copy of Delphi in a VM ... My notebook has 2 gigabytes RAM and a Core2Duo with virtualization ...
    (borland.public.delphi.non-technical)
  • D3 project converted to D7 behaves strangely
    ... I had an Delphi 3 project with one form, ... The strange thing is that when i get a runtime error, ... The project is compiled with every debug option i can imagine. ... Checked options in Project->Options: ...
    (comp.lang.pascal.delphi.misc)