Delphi .Net Vs C# .NEt

[Gclinton]

I'm looking for a comparsion of C# to Delphi .net. My company is about
to begin the process of reengineering a Delphi tightly coupled win32
app and a Older Java webclient that uses JSP over to an ASP.net app.
We are trying to decide if it will be easier just to port some of our
code over to Delphi .net or just to re-write the entire thing in C#.
From what I've seen at the borland confernce the new Borland IDE looks
a lot like the MS .NET IDE. One of the issues is that we have members
of the team that are strong supporters of Delphi and others that are
JAVA and C#. So we are having a hard time deciding which way would be
the best for the future of the app. What I'm looking for is some
"Un-bias" documentation I can share with the group to try and help us
make the decision. One of the concerns about going with Delphi is the
release date of Diamonback which may not be until next year and we
need to start on this by the end of the year. Any information on this
ould be greatly appreciated
TIA,
Greg

[Rob Teixeira]

Well, the one thing I do know for certain, is that a lot of the IDE was
licensed code from Microsoft's product (which is why it looks so familiar).

Honestly though, I think you'll be quarreling over tiny details. Overall, C#
and Delphi for .NET are pretty similar in capabilities. Most of the heavy
lifting is actually done by the .NET runtime, which both share. It's
possible that the deciding factor is more or less the comfort level the team
has as a whole with one language or the other.

I used Borland products for ages (actually started my major programming
efforts with Turbo Pascal, Turbo C++, and Assembler). In terms of Delphi,
it's always been a strong product, but my major "con" for it has always been
that in the Windows world, they always seem to be a step or two behind. It's
to be expected considering MS is making all the rules, but there you have
it.

-Rob Teixeira

"Gclinton" <gc********@msn .com> wrote in message
news:35******** *************** ***@posting.goo gle.com...

I'm looking for a comparsion of C# to Delphi .net. My company is about
to begin the process of reengineering a Delphi tightly coupled win32
app and a Older Java webclient that uses JSP over to an ASP.net app.
We are trying to decide if it will be easier just to port some of our
code over to Delphi .net or just to re-write the entire thing in C#.
From what I've seen at the borland confernce the new Borland IDE looks
a lot like the MS .NET IDE. One of the issues is that we have members
of the team that are strong supporters of Delphi and others that are
JAVA and C#. So we are having a hard time deciding which way would be
the best for the future of the app. What I'm looking for is some
"Un-bias" documentation I can share with the group to try and help us
make the decision. One of the concerns about going with Delphi is the
release date of Diamonback which may not be until next year and we
need to start on this by the end of the year. Any information on this
ould be greatly appreciated
TIA,
Greg

[Alexander Muylaert]

Me,

a higly experienced Delphi developer, always sworn my loyalti to Delphi

Switched to C#

because
1. D8 => really bad
2. C# ==> $1500 D8, 9 ==> $3500 (and it does exactly the same)

3.
Delphi just wrappes again all the .net classes to make them compatible with
VCL. This makes that you have to supply a zillion borland assembliess with
your application. A deplay of a c# app is 500K - framework. A delphi app
=> 500K + a couple of megs on borland assemblies.

4. Delphi 8 code ==> Visual studio ==> NO WAY
VisStudio ==> Delphi 8 ==> Works
(This might be fun for components)

5. Boottime of Visual studio on my PC => 20 seconds
Boottime of Delphi 8 => 3 minutes

6. Delphi never got the tooltip window responding on the same day. Visual
studio does.

7. Don't tell the price difference to your manager or the choice is made.

kind regards

Alexander

[Eric]

There's a *LOT* of books about C# programming, but only one on Delphi for .NET.

There's tons of Internet pages about C#, but only a small number for Delphi for .NET.

Borland has not been doing well in recent years...Delphi 8 was such a buggy release that they have given up on it after making 3 attempts to fix bugs with incremental updates. Boland is now planning on fixing most of the problems, and it's only going to cost you an arm and a leg to get these fixes in the form of the next Delphi release.

Delphi 7 (their last pre-.NET release) is still the best platform for developing native Windows applications. But I don't see myself following Borland in the future.

Eric

[Marc Scheuner [MVP ADSI]]

>3.

Delphi just wrappes again all the .net classes to make them compatible with
VCL.
*IF* you want to !! Using the VCL.NET can significantly ease your move
to .NET - but of course, Delphi for .NET being a full-blown .NET
programming language, you can just as well write straight Windows
Forms and ASP.NET apps - no Borland assemblies needed - NOT AT ALL.
5. Boottime of Visual studio on my PC => 20 seconds
Boottime of Delphi 8 => 3 minutes

And how is that relevant to your users, to the folks using your
software in the end?

Marc
=============== =============== =============== =============== ====
Marc Scheuner May The Source Be With You!
Bern, Switzerland m.scheuner(at)i nova.ch

[Marc Scheuner [MVP ADSI]]

>I'm looking for a comparsion of C# to Delphi .net. My company is about

to begin the process of reengineering a Delphi tightly coupled win32
app and a Older Java webclient that uses JSP over to an ASP.net app.
We are trying to decide if it will be easier just to port some of our
code over to Delphi .net or just to re-write the entire thing in C#.

Delphi for .NET certainly gives you a much easier, much smoother
transition into .NET - and it's just as capable as C#.

Also, with .NET, you could easily convert your existing apps using
Delphi for .NET, and start writing new stuff in C# - heck, Delphi 2005
even INCLUDES C# in the box.

..NET makes it REAL easy to mix and match languages - do some stuff in
Delphi for .NET (where you have lots of Delphi code already), do other
things in C#, yet other in (shudder) VB.NET or whatever - you're
totally free. You can even inherit and extend your Delphi classes in
C# - and vice versa! No more barriers here.....

Marc

=============== =============== =============== =============== ====
Marc Scheuner May The Source Be With You!
Bern, Switzerland m.scheuner(at)i nova.ch

[Alexander Muylaert]

> And how is that relevant to your users, to the folks using your

software in the end?

It is not. Nor did I say so. It is important to me. I don't like waiting.
I do delphi since 93, I'm pretty used of restarting delphi a couple of time
a day. Shift-Ctrl-Esc, Kill process, restart... If one waits 5 times 3
minutes a day, a crew of 4 waits 1 hour. Thats $150.

Delphi itself is not unstable. It is just in combination with me, so I'm
guilty. But on the other hand. Visual studio only crashed once for the
past 9 months. And I'm using it also pretty much.

Kind regards

Alexander

[Marc Scheuner [MVP ADSI]]

>But on the other hand. Visual studio only crashed once for the

past 9 months. And I'm using it also pretty much.

Lucky you!! For me, it crashes at least 3, 4 times every day - and I
don't get a 20 second boot-time either, like you mentioned - quite the
contrary, VS.NET takes a LOT longer to load than any version of Delphi
I've ever used.......

Marc
=============== =============== =============== =============== ====
Marc Scheuner May The Source Be With You!
Bern, Switzerland m.scheuner(at)i nova.ch

[Marc Scheuner [MVP ADSI]]

>But on the other hand. Visual studio only crashed once for the

past 9 months. And I'm using it also pretty much.

Lucky you!! For me, it crashes at least 3, 4 times every day - and I
don't get a 20 second boot-time either, like you mentioned - quite the
contrary, VS.NET takes a LOT longer to load than any version of Delphi
I've ever used.......

Marc
=============== =============== =============== =============== ====
Marc Scheuner May The Source Be With You!
Bern, Switzerland m.scheuner(at)i nova.ch

[Joe Mayo]

Hi Greg,

Here's Glen Stephens' C# for Delphi Developers article:

http://www.glennstephens.com.au/tech...Developers.pdf

Here is another comparison, but not as comprehensive:

http://www.gekko-software.nl/DotNet/Art01.htm

Joe
--
http://www.csharp-station.com

"Gclinton" <gc********@msn .com> wrote in message
news:35******** *************** ***@posting.goo gle.com...

I'm looking for a comparsion of C# to Delphi .net. My company is about
to begin the process of reengineering a Delphi tightly coupled win32
app and a Older Java webclient that uses JSP over to an ASP.net app.
We are trying to decide if it will be easier just to port some of our
code over to Delphi .net or just to re-write the entire thing in C#.
From what I've seen at the borland confernce the new Borland IDE looks
a lot like the MS .NET IDE. One of the issues is that we have members
of the team that are strong supporters of Delphi and others that are
JAVA and C#. So we are having a hard time deciding which way would be
the best for the future of the app. What I'm looking for is some
"Un-bias" documentation I can share with the group to try and help us
make the decision. One of the concerns about going with Delphi is the
release date of Diamonback which may not be until next year and we
need to start on this by the end of the year. Any information on this
ould be greatly appreciated
TIA,
Greg