Re: I have seen some fat client Dot Net apps

Bruce McGee wrote:
Single source for the language
and libraries (more important imo) but without preventing me from
taking advantage of features only available on one or the other
platform.

FMPOV, it does prevent me from taking advantage of the other platform.
The biggest hurdle in porting existing Win32 -> .NET is third party
component incompatibility. VCL.NET hasn't been embraced to the degree
necessary.

The reason is simple; and it's the same as the reason why many Delphi
developers haven't embraced .NET. There's not significant enough
benefit to recompile/port one's Win32 codebase to .NET.

I don't see a divide, I see options. As a wise man once said, "It's
all about the love."

The problem with the options provided is that none of them are good
ones. IOW, I don't see an option provided by CodeGear to incrementally
add .NET to my Win32 projects.

The CodeGear way to leverage .NET is to recompile everything and use
VCL.NET. This is a non-starter if you happen to use components that
don't support VCL.NET.

Feel free to nit-pick about specific minutiae.

I believe considering the specific .NET options provided by Delphi for
..NET to be *very* relevant. 2.0 is pending, but extremely late,
probably too late. CF support is no where to be found.

ISTM the most compelling option provided to the Delphi developer for
..NET development is Visual Studio.

--
Brian Moelk
Brain Endeavor LLC
bmoelk@xxxxxxxxxxxxxxxxxxxxxxxxxxxx
.

Relevant Pages