Comments on: Delphi 2007 and C++Builder 2007 update #2 is now available

By: Unbelief

Unbelief — Tue, 11 Sep 2007 00:21:44 +0000

When will you understand. It’s not the new functionality which is so badly needed, but a STABLE environment…

By: Johan Visser

Johan Visser — Fri, 24 Aug 2007 02:50:04 +0000

What is this?
I have to uninstall Delphi and then reinstall it with cache?

I've looked inside the box, but there isn't a spare harddrive inside.
I can't loose that much diskspace just for an update.
Reinstalling will take more than a day. (uninstall, reinstall, install all extra components)

From this day, we will fase out Delphi and switch to Visual Studio. (Cheaper, more stable, better support)

I say Delphi IS DEAD.

By: Ronald Janse

Ronald Janse — Mon, 20 Aug 2007 23:16:06 +0000

I hoped something would change with D2007.

We skipped 2005, stopped using 2006 and now we have D2007 and it still sucks. When I read all the above, I put D2007 on the shelf and wait until this nighmare is over. I having a really hard time to still defend Delphi when I’m not sure about it myself anymore….. This could cost us a LOT of money.

By: lenn dolling

lenn dolling — Mon, 20 Aug 2007 02:25:46 +0000

like wtf.. I was hoping with CTRL+LMB on a identifer would be working in the update2… I have yet to install the update1… Please say it isn’t so.

lenn dolling

whitecrow.ca

By: x

Mon, 13 Aug 2007 05:04:32 +0000

Almost nothing solved for Delphi in this second patch. I don’t use Delphi anymore since even with Update 1 the stability and quality was still terrible! I’m already a happy VS.NET user. You lost one more.

Bugs & annoyances that have made me stop using Delphi:

1. when opening a project with form XXX.pas, after that opening another project with it’s own XXX.pas, if you CTRL+ENTER on this unitname it will often open the file from the previous project.

2. CTRL+LEFTMOUSE CLICK on identifiers to go to their declaration generally doesn’t work.

3. Get lot’s of exceptions from the Delphi product itself. (note that I don’t have any thirdparty tools/components installed!)

4. Help sucks.

5. Install sucks.

By: David R. Robinson

David R. Robinson — Sat, 11 Aug 2007 18:53:15 +0000

Microsoft’s installers have always been inefficient, stupid, slow and problematic. I always used Wise for my installers and never had problems while everyone else did. I changed companies in 2003 and we used InstallShield/MSI for our installer. After two years of nightmares for both us and our customers and nearly losing two huge customers because they couldn’t deploy our product to their end users, I replaced it with InnoSetup.

The new installer workeds perfectly, is lightning fast. Client deployment works flawlessly, upgrades work flawlessly. The client installer on the new one finishes in seconds. The old installer couldn’t even initialize MSI in the time that the new installer completes.

Just because MSI is the only certified installer that MS is forcing down everyone’s throat doesn’t mean you have to use it.

Stop using MSI and your installer nightmare will go away.

By: Albert

Albert — Sat, 11 Aug 2007 05:47:21 +0000

The isue might become even more problematic when having other CodeGear products installed like PHP. The registration is somehow connected and having problems with one product will interfere with other products. So be aware that you can end up with both products screwed up. Since the amount of installation times is limited you might encounter this problem too as we did. Yes, the service desk was very helpful and the issue finaly solved, but it took a huge amount of time (since the timelap of EU and VS is large) as well of installation times (first the cd, then the full products download of both products etc. etc.). I desperately am needing the old way (D6) of installation, this is only bothering the legal and paying user community and won’t stop any illegal versions, in fact will only stimulate the latter imho.

albert drent

aducom software

By: ahmoy

ahmoy — Fri, 10 Aug 2007 23:50:43 +0000

there are 2 options left for delphi user
a. continues with installing this very very slow process for update 2 (it will take forever, mind you)
b. ignores the update 2, pretends there is no such update!

for me, i will go for options 2 since there is no way i wanna go for this process again, unless the update touches a lot of areas.

just wonder how difficult for codegear makes a drastic change for a new installer? yes, codegear already invested money on this 'installer' but then please think on how difficult for the users to use it

thanks
ahmoy

By: Fernando Madruga

Fernando Madruga — Fri, 10 Aug 2007 08:09:08 +0000

I haven’t even checked the install notes, but even if you guys magically found a way of fixing all the wrongs, it would still not justify the extra length of work to go through that "wonderful" install/update technology of yours.

After loosing a few hours installing Update 1, I won’t be touching another update until you guys learn to do them right. There’s just not enough in them to warrant that huge amount of time… And don’t be surprised if you start loosing customers while you still haven’t got them to trust you after releasing a product that was clearly not ready to ship when it did…

In my point of view, two major problems still exist in Delphi 2007 that need urgent attention:

1) Still incomplete and bugged Help, many times it’s just a waste of time to try and find some information there;

2) Either a lousy installer is used, or a lousy work at creating the install scripts is being done on your side. It may have solved some problems on "your" end (at least, I want to believe it has!), but it surely is the WORST install/update procedures EVER to exist on Borland/Inprise/Borland/CodeGear…

These two, clearly don’t work with "Improving User Experience"; as they are implemented now, they work AGAINST improving user experience…

Sincerely,

Fernando Madruga

P.S.: I’m submitting a copy of this comment to Jim Douglas, FWIW…

By: Jim

Jim — Fri, 10 Aug 2007 05:56:23 +0000

Will just using the default options solve the problem?