If you use Delphi, C# Builder is a natural choice for C#.
From: Bruce McGee (bmcgee_at_glooscap.com)
Date: 16 Apr 2004 11:45:49 -0700
Lee Grissom wrote:
> I must have counted dozens of postings on this newsgroup where when
> the conversation mentions C#, the only tool mentioned is VS.NET.
> Borland needs to devise a strategy to raise awareness of C#Builder b/c
> even it's own customers (ala Delphites) dismiss it as an option. I
> guess my point is moot, since I predict ther'll just be a single
> Borland Dev Studio one day that supports C# and Delphi (Win32/.NET)
> all together.
You make a good point, and I'm guilty of the same assumption. I guess
most of the people I know that are leaving Delphi are also dropping the
rest of Borland's tools so aren't interested in looking at C# Builder.
I find it tougher to defend than Delphi, too. It has some of the new
IDE features I like (new tool pallet, Together integration, live data
at design time and BDP), but it doesn't have some of the silver bullet
features that Delphi has, like the VCL.Net and a compatible win32
compiler. I'm sure there are more. Since it's essentially the same
IDE, I wonder if C# Builder and Delphi 8 plug ins are compatible...
It would be great to see some information from Borland on why they
think C# Builder is the better choice. Consider this a hint, guys.
I'm dabbling with VS 2003, but unless I run into a real showstopper, my
C# development will be done using C# Builder.