Upgrade woes in Delphi-land - [10:01 AM]

Cass McNutt: "YES, these are definitely my biggest concerns -- the showstoppers that killed my BDS 2006 upgrade attempt, and still currently prevent me from buying Delphi 2007 for Win32." - I find these types of conversations very valid, but strange at the same time. It would seem Delphi's biggest strength is also it's biggest weakness. Third-party components and libraries are the thing holding Cass up. I say stop using all those third party controls if you cannot rely on them to be upgraded for the next rev of Delphi. I'm sure the CodeGear guys get betas out to the third-party guys making these components so they should be able to upgrade their stuff.

Cass, if you want to have the ability to upgrade to the next release when it hits the streets you'll have to depend less on the third-party guys. I hate to say that but it seems to be true in your case. Find a Delphi third-party vendor that stays on top of their game and use only their stuff if you have to use a third-party solution at all.

On the flip side, how many products are you actually shipping and supporting? If it's mainly for your own use and the code continues to work you may not need to upgrade until forced to do so, meaning your copy of Delphi and the code created by it stop working.

You're not the first Delphi guy I've heard with this complaint. There's a company in Fresno still using Delphi 3, or something like that, and still actively maintaining and enhancing that product.

You've enjoyed the benefits of rapid application development, now you're facing the downside. Hang in there, the CodeGear guys are very good and will find a way to help you.

Labels: Development