Delphi 2007 Handbook








November 15, 2006

Debates about Delphi for .NET and VCL.NET

A talk on moving from Delphi to .NET at Microsoft TechEd conference are spawned some online discussion.

Hadi Hariri (of IntraWeb fame) did a talk at the recent Microsoft TechEd in Barcelona discussing if, how, when, and how to convert Delphi Win32 project and where to go for .NET development. Tim Anderson wrote an account. Hadi posted quite a different story. There was debate on newsgroups, and other blog posts.

I think the question of whether to move to .NET, which type of programs, and which .NET user interface (WinForms, WPF) is open, so I don't have much more to add... although I certainly put more value on the VCL.NET project that most others do.

posted by marcocantu @ 0:14AM | 4 Comments [0 Pending]




 

4 Comments

Debates about Delphi for .NET and VCL.NET  

I agree with Hariri: *right now* it would be a bad 
decision to start a new *.NET* app in Delphi and 
VCL.NET. Maybe one day it won't.

Anyway, let's talk about CodeGear now...
Comment by Kent Morwath on November 15, 00:29

Debates about Delphi for .NET and VCL.NET (FUD and more FUD)  

What a load of &!#?#!... Microsoft FUD again..

90% of business I deal with have 'SOE' (Standard
Operating Environments) which doesn't include .NET 2.0

If you can do a job in Win32 and it works.. Why port
to .NET unless you have to ? And if you have to.. Why
not port via VCL.NET ?

Whats Photoshop written in ? Whats Skype written in ?
Whats Office, Project, Oracle, etc etc written in? 

Its not .Net thats for sure..!!

TMSSoftware has a number of great components which are
VCL.NET compatible. So I have flexability of Win32 or
.NET (if I have a need).

WPF is a NATIVE DLL + Wrapper.

Why if Office 2007 not written in .NET 2.0 ?

Why ? Speed/Memory usage etc..

'Highlander' is on the way, and will be .NET 2.0 (well
3.0 minus WPF/Indigo).

VISTA has .NET 3.0 pre-installed..  (which is .NET 2.0
+ libs)

OK.. Great..

So my 'Highlander .NET 2.0 which is actually 3.0 minus
WPF/Indigo' will work FINE.. And nothing stops me from
using ATLAS, WPF, Indigo etc etc with Delphi.NET..

Lets just ignore the FUD and support CodeGear..!!
Comment by Andrew Tierney [http://www.castlesoft.com.au] on November 15, 05:43

Debates about Delphi for .NET and VCL.NET  

I'm not with or against anybody. However, in response
to Andrew's comment, I think it's unfair that you say
things which are actually opposite to what Hadi has
posted on his blog. He actually said that he told
people not to port just for the fact of it and that
Win32 is still alive and kicking.
Comment by Jeffrey Townsend on November 15, 11:48

Debates about Delphi for .NET and VCL.NET  

Delphi for Win32 is good.
Delphi for .NET is good too.
but Delphi VCL.NET is bad.

and VCL Win32/VCL.NET still have no any good(easy,
efficiency)  multi-tier solution like .NET Remoting,
poor Delphi for Win32/VCL.NET.

Chris
Comment by Chris on November 17, 05:57


Post Your Comment

Click here for posting your feedback to this blog.

There are currently 0 pending (unapproved) messages.