A VCL.NET Dangling Question..

From: Edwin Lau (edwin_at_iredsoft.nospam.com)
Date: 02/15/05 

Date: Tue, 15 Feb 2005 18:25:03 +0800

Personally, I like VCL.NET since it is an easy transition for a programmer
such as myself coming from the VCL environment.

I see that there are some people who advocate using pure .NET and I do
not doubt that it is a bad decision. Most of the resources outside are
available
as pure .NET tools and also it is easier to get C# books than Delphi.NET
VCL.NET
based books. There is probably also the issues of less assemblies to
distribute and
all that.

But I understand that the .NET Framework namely v1.1 that we know now would
be replaced by v2.0 which is going to be radically different from what it is
now, at least
as far as what I was told. I did took a look at the Visual Studio Web 2005
and the
ASP.NET has several other rich sets of components. I believe that the .NET
2.0
for desktop would have those too.

I also understand that the new major Microsoft Windows Operating System
which
supports .NET 2.0 framework natively so I guess by that time, the majority
of the
end user (If they upgrade OS) would be .NET 2.0 supported and those programs
if we write now if we use native .NET 1.1 framework would not run without
modification.
That's what I understand.

So that comes back to the issue of VCL.NET. From what I understand, the
VCL.NET
is the .NET rewrite of the VCL class of components which is pretty feature
rich as it
is now compared to the native .NET components. Let's not talk about the 3rd
party
ones available. I would assume that for now, the VCL.NET framework is
dependent on
the .NET 1.1 framework now and that would probably be an issue if someone
with
say Windows 2006 tries to run it as they only have .NET 1.1 framework. But
that is
probably when Delphi 2006 would come with the .NET 2.0 support. So I would
assume
that as a Delphi programmer all I need to do is just recompile the program
(technically
without any code change) and my VCL.NET based application can be .NET 2.0
compliance ?

And that in itself, apart from the ease of transition from the VCL to the
VCL.NET environment
would be made easy with Delphi 2005 or 2006 and above.

Am I right in my assumption ?

Of course, if I were to be looking at the ASP.NET environment then it would
be a different
issue altogether since it is fully based on the ASP.NET framework and not
the VCL.NET
framework and that could explain the components I could use and the language
that I am
using.

Thanks for staying so long to listen to my thoughts.

Edwin

Relevant Pages

  • Re: GWindows and David Botton
    ... GNATCOM + GWindows is nearly complete vs. Delphi/ C++ Builder 2/3 VCL ... The part left is the environment, not the framework per se. ...
    (comp.lang.ada)
  • Re: WDFQUEUEs REQUIRE DISPATCH_LEVEL operation on X64/AMD64 platf
    ... the code is the same but it works properly within only one build environment, ... problem may not be a framework issue but the combinatiion of build and ... Our application using the driver, on our system, is ... WdfDeviceInitAssignWdmIrpPreprocessCallback where the execution level ...
    (microsoft.public.development.device.drivers)
  • Re: Thinking Clearly
    ... very much at the cutting edge; learning how to program for an event driven ... Although VCL provided a massive advantage over VB's dual language ... avoid having to switch frameworks with any new UI framework, ... Learning the language isn't difficult but learning the .NET ...
    (borland.public.delphi.non-technical)
  • Re: A voice from the community
    ... for a "borlander" used to code in delphi with the VCL from the mitic Delphi ... I think the best way for DevCo is not to use a thirty part framework ...
    (borland.public.delphi.non-technical)
  • Re: Vista and .NET (Win32 life may be limted)
    ... To expand the VCL to include all ... .NET lives mostly on the server, ... possibilities in win32. ... they only duplicate the framework. ...
    (borland.public.delphi.non-technical)