Re: Sad & Angry with Delphi 2006 (BDS)

RHR wrote:

Did you upgrade to D2006 from D6? In that case you're also selling
your

I tried to "upgrade" from D6. It turns out that the Win32 part of
BDS is a DOWNGRADE from D6.. It has less functionality and
versatility than D6, not more. I think it's deceptive advertising to
call it an upgrade.

I can't listen to this and not respond. FUD like this just HAS to be
responded to.

How did you do refactoring with D6? Could you slice and dice code
anywhere as quickly, efficiently, and most importantly SAFELY as you
can with BD2006?

Did you have designer guidelines in D6 that helped you position and
align controls easily and perfectly without having to use the clunky
toolbars and dialogs to do so?

Did your D6 VCL apps have built in margin support so that docked
controls weren't slamming up against the edges of their parents?

Did D6 autocomplete your blocks, for loops and other blocks of code for
you, making writing code very fast and productive?

Did you have anything similar to SyncEdit to quickly change identifiers
in any selected scope?

Could you click any identifier and get a pop up window of all the
references to that identifier anywhere in your project?

Could you apply well tested industry-standard design patterns to your
class libraries and model them visually with two-way code?


Why don't you share with everyone some of the things you did in D6 that
are not available to you in BDS2006? When you make the comment: "It
has less functionality and versatility than D6, not more.", you should
expect to be challenged. I've already demonstrated just some of the
Win32 Delphi functionality that's been added since D6, and I could go
on with more. That doesn't even count the Asp.net, C#, and C++ support
in the product, nor does it discuss ECO support and various new goodies.

So, why would I possibly want to go back to D6? What is it I'm missing?

Thanks,

Randy


--

.

Relevant Pages

  • Re: MS Project 2003 Demo
    ... upgrade path for P3 users who have current ... P3e/c is one if those newer Primavera developments, ... make a decision based on the functionality of each. ... >> download. ...
    (microsoft.public.project)
  • Re: **Urgent** New Edit in Datasheet error occurring on proven WSS
    ... We have over 1200 users so our upgrade plans for Office 2007 are not in the ... near future since the user experience will change quite extensively, ... the functionality I decided to attempt some client-based fixes. ... We ended up doing a repair of the WSS2 installation and then an ...
    (microsoft.public.sharepoint.windowsservices)
  • Re: NEWSGROUPS ?
    ... This is where we want to go with this, and you are going to have to upgrade whether you like it or not. ... The only real functionality improvement I can discern is the ability to choose to top or bottom post, and the safety options I guess. ... I'd wager that the number of customers MS has using the NNTP functionality of Exchange was low enough that there isn't that much of an outcry that it is going away. ... But, with PFs going away, the question of how NNTP could be handled without PFs was probably suitably complex that they weren't too concerned there either. ...
    (microsoft.public.outlook)
  • Re: Windows 2000 Mixed to Win2003. What to Expect?
    ... from the upgrade of 3 separate NT4 domains. ... All domains are running in Windows 2000 Mixed mode as a result of the NT4 upgrade, but all domain controllers in all domains are now running Win2003 servers, all Exchange servers have been upgraded to Exchange 2003. ... There are no Win2000 or NT4 domain controllers left on the network and no expectations to need this functionality either. ...
    (microsoft.public.windows.server.active_directory)
  • Re: Uses for Screen OCR technology
    ... Certainly Microsoft is not going to rewrite Win32 or COM ... interfaces that already exist to expose operating system functionality, ... rather will write wrappers that call the existing functions or interfaces ... and expose them in a manner consistent with the .NET framework. ...
    (microsoft.public.vc.mfc)